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

Configuring Contact Center Client to use CCC Chat in an environment with Lync on some systems

$
0
0
Article ID: 52084 - Last Review: July 22, 2015

NOTE:  Contact Center Client Chat is now a return to service only product.  For more information, please see the following article: http://micc.mitel.com/kb/KnowledgebaseArticle52309.aspx

PROBLEM

Your site is using CCC chat, but some client computers also have Microsoft Lync installed.  In version 7 of the MiContact Center software, we auto-detect if Lync is present and set the CCC Chat to Lync Integration by default.  In a mixed environment (where some people have Lync and others don't) you may want to use CCC Chat so that everyone can communicate.  In order to disable Lync integration, a configuration change is required. 

Skype-for-Business / Lync integration can also cause issues with CCC Profiles not loading properly. Users can create and save new user profiles in CCC, but when attempting to re-open these previously saved profiles, the profile does not open / comes up blank. No errors or warning are displayed. "Loading Profile" dialog appears momentarily and then disappears.


INSTRUCTIONS

1. On the Enterprise Server, go to [InstallDir]\CCM\Services\ConfigService\ and open the GlobalAppSettingsEditor application file. (You may need to right-click on it and "Run as administrator".)


2. Type in the following information, exactly as shown.

NOTE: The values are case- sensitive; DO NOT use the drop-down boxes, as the values in the drop-down boxes do not have the proper case, and will not work.)

  • Application: ContactCenterClient.exe
  • SectionGroup: AppSettings
  • Name: UseCccChatOnly
  • Value: true (this is case sensitive)
  • Description:  Enter a description here of why the change is being made.  NOTE: There must be a value entered in this field to save.

3. Click Save.  

NOTE:  It can take 1 to 5 minutes for this value to save.  Wait for the confirmation message before closing the GlobalAppSettingsEditor.


APPLIES TO

7.x

Keywords: CCC Lync mixed Chat Profile not loading blank


CCM/IQ/IVR/VWM Simplified Licensing Matrix

$
0
0
Article ID: 51101 - Last Review: February 23, 2016

SUMMARY

The attachedfiles contain a Matrix for CCM Enterprise Edition, CCM Business Edition, IQ, and IVR/VWM license options in a simplified manner.  There are two files, representing different software versions.

  • Simplified-Licensing-Matrix-58-6001.xls covers versions 5.8 through 6.0 FP1
  • Simplified-Licensing-Matrix-6002.xls covers version 6.0 FP2 to 7.1.3.2
  • Licensing Matrix V8.docx covers versions 8.0.0.0 and above.

NOTE: There are three separate tabs in the excel file for CCM (EE and BE), IQ, and IVR.



APPLIES TO

CCM, IQ version 5.8
CCM , IVR/VWM versions 6.0, 7.0, 7.1, 8.0


Keywords: simplified licensing license matrix ccm iq 6110 6160 5.8 IVR VWM 6.0 7.0 7.1 8.0


Detailed Release Notes - 8.0.0.1

$
0
0
Article ID: 52420 - Last Review: February 24, 2016

INFORMATION

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

 

APPLIES TO

MiCC 8.0.0.1 

Keywords: DRN release notes 8.0.0.1

Queue Real-time statistics inaccurate: SMDR Parsing Error [BadDataField]

$
0
0
Article ID: 52421 - Last Review: February 29, 2016

** Please note that this article may be updated throughout the day as new information is reported from active issues. Please ensure to refresh the article for updates. **

PROBLEM

It was reported that Queue Real-Time statistics on various sites were partially updating beginning on February 29. More commonly, calls handled in Queue Now monitor. Additionally, same day reports could be inaccurate as well until the data is re-summarized.

Looking at the SMDR data file for the day, you can see the following;

Error: 2016-Feb-29 11:20:09.159 Parsing SMDR record - Failed to parse record 02/29 11:18:30 0000:01:38 1870 1870 01706628628 A T9998 101 1011870 A1012426 A . Error BadDataField ()

Similar errors can be found in the prairieFyre.Services.EnterpriseServer.log file.


WORKAROUND

For the errors to subside and resolve the real-time statistic inaccuracies, a restart of the .NET Enterprise Service will be required. While restarting this service could cause Contact Center Clients to temporarily grey out, it could also have other negative impact on the system such as IVR routing issues if Queue conditions are part of your workflow therefore please be cautious before restarting a core service . If it is not possible to restart the service during business hours, please do it at the end of the day. This is only impacting releases other than 8.0 and we believe that this will resolve itself automatically when the date changes to March 1st.

NOTE: The integrity of the reporting data for February 29 will be intact.




APPLIES TO

5.x,6.x,7.x

Keywords: SMDR Parsing Error BadDataField Queue Real Time Statistics

HOWTO - How to manually update the Client Component Pack applications

$
0
0
Article ID: 51439 - Last Review: February 29, 2016

PROBLEM

On a computer where you have just installed the Client Component Pack, when you attempt to start Ignite, it does not start.  

You may see a window that says "Downloading Update" briefly flash and disappear.

You may also see this problem after a server-side software update, you may see these symptoms on PCs where the client software was previously installed.


CAUSES

This problem is generally attributable to one or both of the following:

A)  .Net 4.5 is not installed on the client computer.  This component is required for the client software to function - there is no getting around that requirement.

B)  User Account Control is not disabled on the client computer, causing the Updater Service not to be able to download the updates the software needs to run the first time. 

Note:  In Windows 8, UAC must be disabled in the Registry, by setting the value of EnableLUA to 0 here:  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

Also Note:  On Windows 8 or Windows 7, after disabling UAC, the computer must be restarted.


A less-common cause is network latency from the server to the client machines.


WORKAROUND

If .Net 4.5 is installed, you can do this workaround to update the client applications.

This workaround has two steps:  First, verify that the ManifestIDs have updated (usually, ManifestIDs update, but the actual files do not).  Second, manually copy the application files from the server to the client PC.

You will need access to the MiCC server in order to complete this workaround.

NOTE: You must update all components in order to avoid version mismatch errors.  This includes the prairieFyre Updater Service and the prairieFyre MiAudio Emulation Service.



Verify that the ManifestIDs have updated:

On the MiCC server: 

1.  Open Notepad. 

2.  Browse to [InstallDir]\CCM\Websites\CCMWeb\Applications   (Note:  [InstallDir]\CCM is the default location for a prairieFyre installation.)

3.  Locate IgniteManifest.xml, and drag it into the Notepad window.

4.  Look for the "manifestId=" value in that file, and make a note of the value.


On the client PC:

5.  Browse to [InstallDir]\CCM\Updater\Applications\{b9885822-745d-431e-8776-b6a504290ef3}

6.  Look back at the value you noted in step 4.  There should be a file in the folder here with that name, and the extension .appliedmanifest.


If the file exists, ManifestIDs are updating.  You can now simply copy over the application files you need.

If this file doesn't exist, your ManifestIDs aren't updating; please see the section entitled "Manually Updating the Manifest IDs", at the bottom of this article.


Manually copying over application files:

Determining which files you need to copy:

- You will always need to copy over Appstart.zip and UpdaterService.zip from the server.

- Ignite:  If the user needs Ignite, copy over Ignite.zip

- Contact Center Client:  
- On MiCC for Lync systems, you need to copy over CCSClient.zip  
- In conventional (PBX-based) MiCC environments, you need to copy over CContactCenterClient.zip

- YourSite Explorer:  YSE.zip

- SalesForceIntegration, MbgConnector, and FlexibleReporting (CCM for 3300 only):  Each of these applications will also require the appropriately-named zip file be copied.

Copying the files:

Note:  Before copying over application files, please check the TaskManager > Process tab to ensure the application you are attempting to update is not still silently running in the background.


1. Application files on the server are here:  [InstallDir]\CCM\Websites\CCMWeb\Applications  .  

Each application is in its own subfolder.  There is a zip file in each folder.  It is the zip file you want to copy.   (e.g. [InstallDir]\CCM\Websites\CCMWeb\applications\Ignite\Ignite.zip)


2. For the applications you need (see note below - Determining which client ), copy the appropriate zip files to this directory on the client machine:   [InstallDir]\CCM\Applications .  

Note:  Copy the zip files directly to Applications, not to the subfolder for the application name.  


3. On the client PC, unzip all the zip files you've copied into Applications, overwriting the original folders.



MANUALLY UPDATING MANIFEST IDs (not usually necessary):

If ManifestIDs are not updating automatically, you can update them manually.


For AppStart, and the again for each other client application you need, follow the procedure below to update the manifestID


On the MiCC Server:

1.  Open Notepad. 

2.  Browse to [InstallDir]\CCM\Websites\CCMWeb\Applications

3.  Locate the appropriate ManifestID file, and drag it into the Notepad window.  

- AppStart (you will always need to do this one):  AppStartManifest.xml


- Ignite:  IgniteManifest.xml

- ContactCenter Client:  

- MiCC for Lync environments:  CcsClientManifest.xml
- Conventional (PBX-based) MiCC environments:  CCCManifest.xml

- YourSite Explorer:  YSEManifest.xml

- SalesForce Client:  SalesForceManifest.xml

- Mitel Border Gateway Connector: MbgConnectorManifest.xml

- Flexible Reporting: FlexibleReportingManifest.xml


4.  In the file, look for the section named applicationID= , and note the value.  Then, look for the section named manifestID=, and note the value of that, as well.  (There is a screenshot below with each value highlighted in an example file.)


On the client PC:

5.  On client PC, browse to [InstallDir]\CCM\Updater\Applications

6.  In that folder, browse to the folder where the name matches the application ID you noted in step 4.  (If the folder doesn't exist, create one.  Include the "{}" brackets.)

7.  Within that folder, create a file with this the manifest ID you noted in step 4 as the name, and with the extension  .appliedmanifest .  For example:  995e691-b00f-4e62-a71f-98c64b012dd6.appliedmanifest 


Do this procedure for AppStart, and any other client applications required on the PC.


Screenshot of a sample Application Manifest file:



ADDITIONAL INFORMATION

You can consult this KB Article for an in-depth explanation of how the updater service functions.


APPLIES TO

All versions of MiCC (conventional and for Lync).


Keywords: manually update contact center client applications

 manually update contact center client applications
 manually update contact center client applications
 manually update contact center client applications

MCC - A Voice call, and a Multimedia item are both delivered to an agent when the Workload should allow only one

$
0
0
Article ID: 52422 - Last Review: March 3, 2016

PROBLEM

An agent who's workload is configured to prevent a voice call and a multimedia item from being taken simultaneously is delivered items from both media types at the same time. 




CAUSE

The Workload prevents other medias from delivering items by placing any blocked medias into a Make Busy state (Overloaded).   Because the Voice portion is controlled by a MiVoice Business, and not directly by the MiContact Center server, there is a potential race condition where the Voice media is sent a Make Busy request, but it does not arrive before the MiVoice Business has routed the call.

This will only occur when both voice and multimedia have items queued at the same time, and may still be intermittent.

RESOLUTION

Because of the race condition, the Voice media will always take priority over multimedia.  The easiest solution is to add a small delay to the multimedia delivery so that it can correctly Overload if a voice call is sent right away.

In the InQueue Workflow for any multimedia queues that should defer to voice, add a Delay activity (2 seconds) just above the Offer To Agent activity.

 



APPLIES TO

Multimedia MiCC Version 7.X and newer 

Keywords: workload voice chat email sms simultaneous simultaneously at once

MiCC Version 8.0.0.0 or 8.0.0.1 downloaded before March 3rd, 2016 - Pre-requisite download causes error.

$
0
0
Article ID: 52423 - Last Review: March 3, 2016

PROBLEM

The elasticsearch component downloaded through the chocolatey server during an upgrade, repair, or fresh install of MiCC, was upgraded on the chocolately server yesterday to a version that is incompatible with MiCC.  (Chocolately is a package manager for Windows.)  The result is that elasticsearch will not be functional and MiContact Center components that require it are will not function.

Who is affected?

  • Customers who deploy or repair the old versions of 8.0.0.0 and 8.0.0.1 (downloaded from MOL on or before March 3, 2016) on or after March 2, 2016.

 
Who is not affected?

  • Customers that have already deployed 8.0.0.0 and 8.0.0.1 prior to March 2, 2016.
  • Customers on releases other than 8.x.

What are we doing to fix the problem?

  • The links to 8.0.0.0 and 8.0.0.1 on the Mitel Online page have been temporarily taken down, with a note indicating that we are working to re-post as soon as possible.
  • We are repackaging 8.0.0.0 and 8.0.0.1 with an updated installations cript that will not go to the chocolatey server to get elasticsearch.
  • We will update this KnowledgeBase article to indicate how to take corrective action if the new version of elasticsearch had been installed.
  • A TSB is being sent to all dealers who have already downloaded 8.0.0.0 and 8.0.0.1.
  • This behavior will be fixed for all 8.X releases going forward.

RESOLUTION

We will be adding a verified solution for any installations that are impacted by this issue shortly. 



APPLIES TO

MiCC V 8.0.0.0 and 8.0.0.1 downloaded before March 3. 

Keywords: MiCC install installer download elasticsearch chocolatey

Reports failing when being generated with Excel installed

$
0
0
Article ID: 51258 - Last Review: March 4, 2016

PROBLEM

Reports failing when being generated with Excel installed.


SYMPTOMS

Reports will show in the inbox as failed.


Error     2/2/2016 9:37:42 AM      ReportBase.GenerateReport An exceptionwas encountered while generating the excel report. Excel appears to beinstalled on the machine. The exception was:System.Runtime.InteropServices.COMException (0x800A03EC): Microsoft Excelcannot access the file 'Program Files (x86)\prairieFyre SoftwareInc\CCM\Websites\CCMWeb\applications\'. There are several possible reasons:

 

• The filename or path does not exist.

• The fileis being used by another program.

• Theworkbook you are trying to save has the same name as a currently open workbook.

   atprairieFyre.Reporting.Client.ExcelReportBuilder.BuildReport()

   atprairieFyre.ReportProcessing.ReportBase.GenerateReport(DataSet ds)       

Info      2/2/2016 9:37:42 AM      ReportBase.SaveReport:  Killed Excel process 13020         

Verbose   2/2/2016 9:37:42 AM      ReportStandard.Generate - Startedgenerating a standard report. : 00:00:01.1811288             

Error     2/2/2016 9:37:42 AM      Report generation failure - Failed togenerating report, error was System.Runtime.InteropServices.COMException(0x800706BE): The remote procedure call failed. (Exception from HRESULT:0x800706BE)

   atMicrosoft.Office.Interop.Excel.ApplicationClass.get_Workbooks()

   atprairieFyre.Reporting.Client.ExcelReportBuilder.Dispose()

   atprairieFyre.ReportProcessing.ReportBase.GenerateReport(DataSet ds)

   atprairieFyre.ReportProcessing.ReportBase.PersistReport(DataSet ds)

   atprairieFyre.ReportProcessing.ReportStandard.Generate()

   atprairieFyre.ReportProcessing.ReportBase.GenerateReportsByPriority(Int32numberToGenerate)  


          

CAUSE

The report will fail due to Excel security.


RESOLUTION

Permission for DCOMs "Microsoft Excel Application" are causing issues. Here are the instructions to follow in order to resolve the issue;

  1. Go to Start>Administrative Tools>Component Services>Expand computers>My computer>DCOM Config.
  2. Find Microsoft Excel Application and Right Click and go to Properties.
  3. Under security set all to customize and then edit each one to add the user you are currently logged into with full access.
  4. Launch Excel to test that the error "cannot use object linking and embedding" is gone.
    Note: Excel may re-configure out of box again and click ok to confirm user and initials.
  5. Once you can launch Excel without config on startup and error, your reports should no longer fail.

APPLIES TO

5.x 6.x 7.x

Keywords: Report failing Access denied DCOM object linking embedding Excel installed sql dataset null REP002


Detailed Release Notes - 5.10.9.0

$
0
0
Article ID: 52424 - Last Review: March 4, 2016

INFORMATION

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


APPLIES TO

5.10.9.0

Keywords: DRN releasenotes 5.10.9.0

ALM0021- Data Filing IO Problem

$
0
0
Article ID: 51363 - Last Review: November 24, 2011

DESCRIPTION

This alarm is triggered when the system detects a problem writing files to the hard drive of the prairieFyre CCM server.

SEVERITY

Major

IMPACT

When the hardware isn't functioning properly the software can react in different ways from real time inaccuracies to reporting problems.  If the DISK IO errors are not investigated then it could lead to the server shutting down and permanent data loss.

TROUBLESHOOTING STEPS

Contact your local IT group to troubleshoot the disk IO errors, and contact prairieFyre support if required.

APPLIES TO

CCM 

Keywords: ALM0021

Client and Server Port Requirements

$
0
0
Article ID: 51887 - Last Review: March 7, 2016

SUMMARY

The following article contains a list of the ports required by the Contact Center Solutions suite. This information is useful for IT Administrators, Network Engineers, and Security Professionals for determining firewall exceptions, network routing, and appropriate communication channels when traversing network routes outside of a corporate infrastructure or over internal and external firewalls. Some communication channels are controlled by Mitel (MiTAI, MiAUDIO, and MiNET) and Microsoft (SQL, Exchange, and IIS). While prairieFyre will attempt to ensure that these ports are kept up to date, always refer to the manufacturers published documentation for your appropriate software release version.

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


 

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

1752

TCP

SMDR data collection from PBX

1754

TCP

Traffic data collection from PBX

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

5152

TCP

Multimedia Contact Center communication

5320

TCP

MiTAI communications

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

8000-8001

TCP

MiTAI connection to PBX

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

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

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

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

 

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

 

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
  • prairieFyre MCC Exchange Objects
  • prairieFyre MCC Exchange Setup

 

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

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

 

CFG0046 - There was a problem with the supplied MiXML login information

$
0
0
Article ID: 52425 - Last Review: March 7, 2016

DESCRIPTION

The credentials you have supplied to connect to your media server are invalid or the MiXML service is not started. Check your username and password for typos and try again. 



SEVERITY

Major 



IMPACT

Telephone System Synchronization will fail 



TROUBLESHOOTING STEPS

This problem is often fixed by verifying the following:

  • Check that there are no typos in the supplied username
  • Check that there are no typos in the supplied password
  • Check that the user account exists on the media server and has the 'Log on as Application' option is enabled on the media server.
  • Check that the MiXML service is installed on the enterprise server.
  • Check that the MiXML service is started on the enterprise server.
  • Try restarting the MiXML service on the enterprise server and try again.

 



APPLIES TO

MiCC Version 8.0 and newer 

Keywords: cfg0046 mixml login information problem media server pbx mivb mivoice business mcd sync telephone system synchronization

Event and Alarm Descriptions

$
0
0
Article ID: 51286 - Last Review: March 7, 2016

TABLE OF CONTENT

CCM displays error and event messages to inform you of successful and unsuccessful operations. A subset of the error and event messages have been assigned unique ID numbers in the form ABC####

ALM -- Alarms
ALM0001IVR File synchronization error
ALM0002IVR Missing audio file
ALM0003IVR Port out of service
ALM0004IVR Ports out of service count
ALM0005IVR Calls processed per hour
ALM0006IVR Invalid destination for callback
ALM0007IVR Workflow failed to execute
ALM0008IVR Average time to answer
ALM0009Mitai congestion errors
ALM0010Connection to alarm agent lost
ALM0011Service restart detected
ALM0012High CPU usage
ALM0013Low disk space
ALM0014Low available memory
ALM0015IVR Bad audio file
ALM0016IVR Insufficient out bound ports
ALM0017IVR Port in DND
ALM0018IVR Port not answering
ALM0019IVR UPIQ port deprived
ALM0020IVR phone audio error
ALM0021Data filing IO problem
ALM0022IIS problem
ALM0023MSMQ problem
ALM0024SQL problem
ALM0025License violation
ALM0026Invalid configuration
ALM0027Media server offline
ALM0028Media server data timeout configuration
ALM0029PBX to PC time drift
ALM0030Data collection
ALM0031Data link
ALM0032Messaging service down
ALM0033IQ audio problem?
ALM0034Invalid agent destination callback
ALM0035UPIQ port deprived
ALM0036Maintenance
ALM0037Queue Control
ALM0038Service High memory (bytes)
ALM0039IVR Calls Forwarded
ALM0040Service High CPU usage (%)
ALM0041Client Server Version Mismatch
ALM0042IVR Ports over licensed
ALM0043IVR Not licensed for Web Callbacks
ALM0044No Default Audio Driver Found on Local Box
ALM0045IVR Missing Callflow Device
ALM0046
ALM0047
ALM0048Router Certificate Expiry
ALM0049Listener Offline
ALM0050SIP Drive Low Disk Space
ALM0051SQL Drive Low Disk Space
ALM0052CCM Drive Low Disk Space
ALM0053OS Drive Low Disk Space
ALM0054Resiliency in Effect
ALM0055HCI/CTI/TAPI Call Control Allowed
ALM0056HCI/CTI/TAPI Monitor Allowed
ALM0057Message Waiting
ALM0058Do Not Disturb
ALM0059Public Network Access via DPNSS
ALM0060Recorded Announcement Device
ALM0061SMDR External
ALM0062SMDR Internal
ALM0063Suppress Simulated CCM after ISDN Progress
ALM0064ACD 2000 - Auto Logout Last Agent On No Answer
ALM0065ACD Make Busy Walk Away Codes
ALM0066ACD Real Time Events Feature Level
ALM0067Extended Digit Length
ALM0068MCD - Report Transfers
ALM0069Network Format
ALM0070Report Account Codes
ALM0071Report Incoming Calls
ALM0072Report Internal Calls
ALM0073Report Meter Pulses
ALM0074Report Outgoing Calls
ALM0075SMDR Meter Unit Per Station
ALM0076SMDR Record Transfer
ALM0077System Identification
ALM0078Time Change Reporting
ALM0079Twenty-four Hour Time Reporting
ALM0080ANI/DNIS/ISDN/CLASS Number Delivery Reporting
ALM0081Extended Time To Answer
ALM0082Standardized Network OLI
ALM0083Standardized Call ID Format
ALM0084Report Internal Unanswered Calls
ALM0085SMDR Extended Reporting Level 1
ALM0086SMDR Extended Reporting Level 2
ALM0087Report Attendant Name
ALM0088Account Code Reporting for Internal Calls
ALM0089Path Reporting for Internal ACD2 Calls
ALM0090Enable Agent Group Events
ALM0091Path Real Time Events Enabled
ALM0092SMDR Time Rollback
ALM0093ACD Time Drift
ALM0094System ID Data vs Config Check
ALM0095Missing Devices Alarm
ALM0096Historical Agent Activity Alarm
ALM0097Duplicate System ID withing Cluster
ALM0098You must perform an initial media server synchronization
ALM0099Work timer mismatch between this COS and its associated Queues and Agents
ALM0100MiTAI Link is down
ALM0101IVR Insufficient outbound ports
ALM0102Routing Service General Failure
ALM0103Monitoring agent ringing state not enabled
ALM0104Carrier plan not associated to a media server or trunk group
ALM0105Secondary line use detected for agent(s) and "Ignore agent secondary line activity" is not enabled
ALM0106Calls handled between 11:30pm and 12:30am and "This enterprise operates 24 hours a day" is not enabled
ALM0107OAI Data link is down
ALM0108Uncosted extensions making outbound calls
ALM0110No UPiQ ports programmed on PBX
ALM0111MiTAI failed to initialize
ALM0113MiTAI performed a hotrestart
ALM0114Callback request failed to save
ALM0016Outbound Dialer failed to execute Outbound Call Flow
ALM0117Duplicate reporting numbers present
ALM0118Hotdesking and traditional agent mismatch
ALM0119Windows Search Service is not started
ALM0121Router invalid transfer destination
ALM0122Storage service not polling
ALM0123CCMRouting database is full
ALM0124Items in the mail server Failed folder
ALM0125Emails in FailedRoute state
ALM0126Media server synchronization failed
ALM0129Emails in outbox with exceeded max retries
ALM0133Conversations in Outbox cannot be indexed
ALM0134Conversations cannot be indexed
ALM0135Conversations are missing Tag information
ALM0136Routing Media Service cannot connect to the CCMRouting database
ALM0141Failed to save SMS configuration locally
ALM0142SMS connection creation error
ALM0143Invalid SMS connection configuration
ALM0144Invalid SMS service configuration
ALM0146Update validation mismatch detected
ALM0152Storage path is not accessible from the Storage Service
ALM0153Storage path is not accessible from MCCWa
ALM0155Elasticsearch is down
ALM0156Unable to move emails to Processed folder

CFG - Configuration
CFG0001Configuration Service General Failure
CFG0002Call Accounting Upgrade Failure
CFG0003Multimedia (MCC) Client History Backup Failure
CFG0004CCM Configuration Backup Failure
CFG0005License Server Failure
CFG0006Couldn't disable Dr.Watson
CFG0007Unable to acquire invoker DN for third party join/leave control
CFG0008Unable to unblock CCC ports in the Windows Firewall
CFG0009Configuration Wizard Unable to Configure CCMWeb for Windows Authentication
CFG0010Unable to configure CCMWeb for Anonymous Authentication
CFG0011SIP Address or Line URI Already in Use
CFG0012An agent shift lasted past midnight
CFG0013A Front End time is not synchronized to the Router time
CFG0014Unable to Monitor Performance Counter
CFG0015YSE: Import CSV general error
CFG0016YSE: Email server connection test general error
CFG0017Support package creation general error
CFG0019Couldn't load license agreement file
CFG0021Microsoft IIS is not installed
CFG0022Not enough hard drive space
CFG0023Not enough RAM
CFG0024Missing deployment package
CFG0025Login attempt without adequate licensing to manage the web site
CFG0026YSE Profile Mismatch
CFG0036Cannot connect to RealTime server
CFG0042Powershell 2.0 not installed
CFG0043The Powershell Lync module is not installed
CFG0044There was a problem communicating with PBX
CFG0045There was a problem with your credentials
CFG0046There was a problem with the supplied MiXML login
CFG0048An unknown error occurred on the media server
CFG0049Workstation has lost trust with the domain
CFG0050An object has already been modified
CFG0051Enterprise IP address not found in registry

VWM - Visual Workflow Manager
VWM0001IVR Callback Make Call failed
VWM0002IVR Callback Calling Customer Invalid Phone Number
VWM0003No Callflow Associated with Port
VWM0004Port Is Associated With Another Server
VWM0005Port's Virtual Identifier is Invalid
VWM0006Config Service not Running and No DSTourSite in Cache Folder
VWM0007Tap Call Delayed More Than 100 Times
VWM0008Tap Call Failed
VWM0009Duplicate Dialable for Queue Detected
VWM0010Realtime Events Disabled for Queue
VWM0011Could Not Connect to Excel File
VWM0012Port Out Of Service
VWM0013Port Not Monitored
VWM0014Failed to Connect to MiTAI Proxy Server
VWM0015Enterprise Server Real-time Trace Buffer Overflow
VWM0016Invalid Hunt Group Members Detected
VWM0017No Sound Card Detected
VWM0018Invalid Audio File Detected
VWM0019Outbound Dialer Failed to Execute the Outbound Callflow
VWM0020IVR Node is missing
VWM0021No UPiQ ports assigned
VWM0022CallReceivedEvent Queue is filling up
VWM0023Transfer activity invalid destination
VWM0024Call flow creation exceeded 4 seconds
VWM0025IVR port failed to transfer call due to MiTAI error
VWM0026PowerShell disabled on IVRInbound/IVROutbound system
VWM0027WebService configuration out of date

MPS - MiTAI Proxy Server
MPS0001Failed to Open MiTAI Connection to PBX

REP - Reporting
REP0001Distribution - Can Not Print Excel Report When Protected View is Enabled
REP0002Excel Not Installed
REP0003Exception Thrown on Attempt to Kill Process
REP0004Generate Report - Data Limit Exceeded
REP0005Generate Report - Column Limit Exceeded
REP0006Generate Report - Out Of Memory Exception
REP0007Invalid Default Printer
REP0008No Default Printer
REP0009Report Distribution - Preferred Printer Unavailable
REP0010Report Distribution - Print Locally
REP0011No Printers Available
REP0012Unknown Error
REP0013Report Distribution - Available Printers
REP0014Unknown Error Checking for Installed Printers
REP0015Forecast Report - Unable to Export Forecast to Excel from CCC or WFS
REP0016Reporting parameter missing. Using default.
REP0017No report parameter, No default available, setting state failed
REP0018Report failed to generate. Invalid report parameters
REP0019Unable to determine the type of report to generate
REP0020Failed to set the current thread to the specified user
REP0021No file to distribute
REP0022Failed to print to PDF
REP0023Report failed to print locally
REP0024PDF report failed to generate

CaR - Call Recording
CAR0001Oaisys Call Not In Progress During Call Tagging
CAR0002License not available
CAR0003Could not reach OAISYS server

SMA - Service Monitoring Agent
SMA0001Unable to Connect to the Service Monitoring Agent
SMA0002Monitored Services Disabled
SMA0003Alarm Has Expired and Will Be Cleared

MAD - Maintenance Alarm Dispatcher
MAD0001Unable to Connect to the Maintenance Alarm Dispatcher
MAD0002Unable to Connect to the Alarm Feed
MAD0003Unable to Find the SNMP Memory Mapped File

DSS - Data Synchrtonization Service
DSS0001Unable to Access an Active Directory (AD) Object
DSS0002Multiple media servers with same IP address
DSS0003Synchronization failed due to MiXML error
DSS0004Synchronization failed due to Intertel error
DSS0005Synchronization failed due to Active directory error
DSS0006Synchronization failed due to Commit error
DSS0007Synchronization failed due to Unknown error
DSS0008Queue conversion failure

IGN - Ignite
IGN0001Cannot sign in to Ignite
IGN0002IVQ panel is missing when Ignite is launched
IGN0003Ignite no longer offers Agent Control features
IGN0004Ignite no longer responding after long period of time
IGN0005Ignite stops functioning correctly
IGN0006Requested media item not found

ELS - Elasticsearch
ELS0001Elasticsearch sniffing error caught. Unable to connect to Elasticsearch server.

Keywords: Event Descriptions Alarm

HowTo - Check the sizes of individual tables in SQL

$
0
0
Article ID: 52426 - Last Review: March 9, 2016

PROBLEM

Your CCMData SQL database is growing, and you want to identify which table or tables are accounting for the size. 


RESOLUTION

1. Download the attached TableSizes.ZIP to the SQL server (or any server with SQL Management Studio able to connect to your SQL server)
2. Unzip the file and run the TableSizes.SQL file 



APPLIES TO

MiCC all versions 

Keywords: SQL database table size sizes growing

Detailed Release Notes - 7.1.3.2

$
0
0
Article ID: 52427 - Last Review: March 11, 2016

INFORMATION

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





APPLIES TO

MiCC 7.1.3.2 

Keywords: detailed release notes drn 7.1.3.2


8.0 - How to apply AMC licenses included with your MiCC Bundle

$
0
0
Article ID: 52408 - Last Review: , 2016

INFORMATION

The attached document contains information about applying AMC licensing included with your MiContact Center bundle.



APPLIES TO

MiCC 8.X 

Keywords: AMC licensing MiCC MiContact Center bundle

ALM0031 - Data Link

$
0
0
Article ID: 51373 - Last Review: March 17, 2016

DESCRIPTION

This alarm indicates communication problems between the MiContact Center server and the PBX that it is communicating with.

SEVERITY

Critical

IMPACT

The result of the data loss between the MiContact Center server and the PBX could result in real time inaccuracies, reporting accuracies and a loss of historical reporting data.

TROUBLESHOOTING STEPS

Follow this article to troubleshoot Data Collection. 



APPLIES TO

MiCC all versions

Keywords: ALM0031

IVR prompts or RADs not playing

$
0
0
Article ID: 52428 - Last Review: March 18, 2016

PROBLEM

Prompts cease to play on certain IVR ports when using an MSL based MiVB platform. Ports start to return RNA (ring no answer warnings). Ultimately this can lead to the MitaiProxyServer service crashing. 



SYMPTOMS

IVR port logging reporting that the TX channel is closed indicated in the logs by TXOpened [False]:

Error: 2015-Dec-11 10:03:53.029   prairieFyre.Routing.Mitel.Implementation.PlayPromptImplementation - TX is still NOT open after 2500ms. Playing Prompt anyway.    (39053 - 192.168.40.90)
Info: 2015-Dec-11 10:03:53.029   prairieFyre.Routing.Mitel.Implementation.PlayPromptImplementation - TX opened, playing Prompt...    (39053 - 192.168.40.90)
Info: 2015-Dec-11 10:03:53.029   prairieFyre.Routing.Mitel.MitelInboundDevice - Playing Prompt Member [Static[No one available.wav (File)]]    (39053 - 192.168.40.90)
Info: 2015-Dec-11 10:03:53.029   Playing [C:\Program Files (x86)\prairieFyre Software Inc\CCM\Ivr\Media\Custom\en-GB\No one available.wav] - TXOpened [False] - RXOpened [False].    (39053 - 192.168.40.90)
Error: 2015-Dec-11 10:03:53.029   Cannot play wave file - rc = [FAILED_OPERATION].                        (39053 - 192.168.40.90)
Info: 2015-Dec-11 10:03:53.029   MiAUDIO - Audio EVENT Received: WAVE_OUT_ERROR.                        (39053 - 192.168.40.90)
Info: 2015-Dec-11 10:03:53.029   prairieFyre.Routing.Mitel.MitelInboundDevice - Received AudioStatus: [WAVE_OUT_ERROR]    (39053 - 192.168.40.90)
Error: 2015-Dec-11 10:03:53.029   prairieFyre.Routing.Mitel.MitelInboundDevice - Wave out Error Detected    (39053 - 192.168.40.90)

May also cause alarm ALM0015 - IVR Bad Audio File to be fired.

 



CAUSE

This is caused by a media server fault in MSL based MiVB platforms running versions earlier than MiVB 7.2.   



 

WORKAROUND

A reboot of the MiVB that the ports reside on resolves the issue temporarily.


RESOLUTION

 Upgrade the MiVB's to release 7.2 or above. This was resolved due to a code re-work to address multiple media server issues.



APPLIES TO

MiVB releases prior to 7.2 

Keywords: TXOpened, ALM0015, RAD, Prompt, RNA, MitaiProxyServer

EMail server configuration - Google Apps for Business

$
0
0
Article ID: 51960 - Last Review: March 24, 2016

CONFIGURING YOUR GOOGLE APPS FOR BUSINESS ACCOUNT

To create a new user

NOTE: Google charges based on number of users, so creating new accounts will increase your monthly bill.

1. Sign in to the Google Admin console.
2. Click Users.
3. Select the organizational unit to which you want to add the user.
4. Click the Add User icon in the new Admin console, or Add users if you are in the classic Admin console.
5. Select the Create user manually option and click Continue.
6. Enter the new user's First Name, Last Name, and Primary email address in the appropriate fields.
7. If applicable, select the home domain for the user.
8. (Optional) Set the user’s initial password.
9. Click Create new user.
10. Click Done.

NOTE:  Google mail accounts created after September 15, 2015 will require the allow less secure apps setting to be enabled.  For more information, please see the following link:  https://www.google.com/settings/u/0/security/lesssecureapps


To enable IMAP in Google Apps for Business
1. Sign in to the Google Admin console.
2. Do one of the following:
  • In the classic Admin console, click Settings =>Gmail.
  • In the new Admin console, click Google Apps  =>Gmail  =>Advanced settings.
3. In the Organizations section, highlight your domain or the organizational unit for which you want to configure settings (see Configure email settings for an organizational unit for more details).
4. Under POP and IMAP Access, clear the check box for Disable POP and IMAP access for all users in the domain.
5. Log into GMail using each user, and enable IMAP under the Forwarding and POP/IMAP section.



IMAP and SMTP Settings

When configuring the prairieFyre software, you will need incoming and outgoing email settings.

OUTGOING
SMTP Server:  smtp.gmail.com
Use SSL: Yes
SMTP Port: 587
Connection Timeout: 30

From Name: default sender name
From Email Address: default sending email address

SMTP Authentication Required: Yes
Username: Full email address
Password: Password
Domain: Your domain

INCOMING
Enable Incoming Server Settings: Yes
Use TLS: Yes
Incoming Server: imap.gmail.com
Incoming Port: 993
Connection Timeout: 30
Incoming Folder: Inbox
Incoming Logon Information... Same as Outgoing Server: Yes


CREATING AN EMAIL ALIAS


prairieFyre recommends creating one email address with multiple aliases.

An email alias is an alternative email address that points to an existing user account. For example, the user bill@subsidiary.com might also want to receive email addressed to william@subsidiary.com. If you create william@subsidiary.com as an email alias for bill@subsidiary.com, Google Apps will deliver email for both of these addresses to the same Gmail inbox.

1. Sign in to the Google Apps administrator control panel.

The URL is
https://www.google.com/a/cpanel/primary-domain-name, where primary-domain-name is the domain name you used to sign up for Google Apps.

2. Find the user account which was created for EMail queues.  You can use either the Search or Browse function.

  • Search: Enter the user name in the search box at the top of the Google Apps control panel, then click Search accounts.
  • Browse: Click the Organization & users tab from the top menu. Select an organization from the organizational structure on the left.

3.  Click the row for the user account.  This will display the user information page.

4. Click Add a nickname.

5. Enter the desired username into the provided text box. (The username will be the portion before the @ symbol in the email address)

6. Select the domain for the nickname.

If you have secondary domains associated with your Google Apps account, the field to the right of the @ sign is a drop-down list with the available domains. The domain you select will be the portion of the user's email address that appears after the @ sign. (If you have a domain alias for your primary domain, every email address in the primary domain automatically has an email alias address in the alias domain.)

7. Click Save Changes.



CREATING A SEND-FROM ALIAS 

This configuration is required so the agents can send using the email addresses represented by the queues (i.e. support @pf.com or sales@pf.com)  using one email account.

Gmail lets you send messages with another of your email addresses listed as the sender instead of your Gmail address. This feature helps you manage multiple accounts from the Gmail interface; it works only if you already own the email account linked to the alternate address. To send mail from a different Gmail username, you'll first need to sign up for that address. Select an option below for instructions on how to add your other addresses to your Gmail account.

To be able to proceed, you will need:

1. Log in to Google Apps inbox.
2. Go to Settings/Accounts.
3. Click on Add another email address you own.
4. In the field Email address, enter your nickname (see above).
5. Click on Next step.
6. Now, click on Send verification. This will send an email to the specified nickname, which just is an alias for your email address. That means that the email will be sent to your inbox.
7. Click on Close window and go to your Inbox.
8. You should have a new email in your inbox with the title “Organization name Confirmation – Send Mail as nickname@domain.com. Click on the long link in the email.
9. Go to Settings/Accounts. Under Send email as, choose the option “Reply from the same address the message was sent to“.

To test your new nickname:

1. Click on Compose mail.
2. In the From field, select the nickname.
3. Enter your Google Apps accounts username in the To field.
4. Enter a subject in the Subject field, and some text in the text box.
5. Click on Send.
6. Go your Inbox and check for a new email.  This message should display that it came from the nickname.

You can have multiple nicknames.  If you have more nicknames, just follow the first 8 steps for those names too.
 

APPLIES TO

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

Keywords: Atlantic MCC email gmail nickname alias queue queues

HowTo: Recreate the PFDSCACHE files safely

$
0
0
Article ID: 51892 - Last Review: March 24, 2016

INFORMATION

Under some circumstances deleting the PFDSCACHE is recommended in order to clear the cached data.   In order to do this safely, we recommend deleting specific items, rather than the entire folder.

Deleting the PbxConfig file in a multi-PBX environment can cause problems if a manual Telephone System Synchronization is performed, resulting in devices from other PBXs being disabled.  Note also, that any exclusion list you have configured for telephone system synchronization will be lost.  If you delete the PbxConfig folder, you must run an Enterprise Telephone System Settings Synchronization immediately (a sync that has all devices starting at the enterprise checked). 

Deleting the LocationTree file is not necessary, unless troubleshooting telephone system synchronization issues.  The folder will be recreated by saving a change to a phone number in YourSite Explorer.  You can also recreate it by restarting the Config service, however this is very processor intensive, taking several minutes and using an entire core of CPU for the process.  We recommend using the phone number change to recreate this file.



INSTRUCTIONS

1. Go to YourSite Explorer.
2. Click the Tools tab at the top.
3. Click Reset Clients.  This will push the configuration to all clients again.

If this does not work, then try deleting the pfdscache.
1. Go to C:\ProgramData\pfdscache\
    NOTE: The \ProgramData\ folder is hidden. You will need to ensure that you can view hidden files and folders.
2. Delete or move to a backup location all files that begin with CACHE.
3. Do not delete the PbxConfig file or the LocationTree unless deemed necessary (telephone system synchronization issues will sometimes require these to be recreated).



APPLIES TO

CCM and CCC 

Keywords: recreate delete pfdscache howto telephone system synchronization sync manual disabled historical

Viewing all 959 articles
Browse latest View live