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

DSS0005 - Telephone System Synchronization failed due to Active Directory

$
0
0
Article ID: 51723 - Last Review: May 7, 2015

DESCRIPTION

The telephone system synchronization failed and the area of its failure was Active directory.

SEVERITY

Error

IMPACT

The telephone system synchronization did not complete. 



TROUBLESHOOTING STEPS

Checking the telephone system synchronization logs may indicate what caused the error. Telephone System Synchronization logs can be found in [Install Path]\CCM\Logs\ look for the prairieFyre.Services.DataSynchronizationService.TXT file.

1. Ensure that the Enterprise Server can reach the Domain Controller.
2. Ensure that the Enterprise Server is a member of the Domain. 



APPLIES TO

6.0.2.0 and newer

Keywords: DSS0005 sync synchronize telephone system synchronization active directory domain even alarm


ALM0054 - Resiliency in Effect

$
0
0
Article ID: 51547 - Last Review: May 8, 2015

DESCRIPTION

The CCM server has detected that one or more devices being monitored have failed over to their resilient controller.



SEVERITY

Minor 



IMPACT

None.  This alarm is only an indicator that resiliency has been detected.



APPLIES TO

7.0 and newer

Keywords: Resiliency in Effect ALM0054

IVR - Importing the sample PCI Compliant workflow becomes blank when reloaded

$
0
0
Article ID: 52279 - Last Review: May 11, 2015

PROBLEM

After importing the Sample Workflow for PCI Compliant Systems, correcting all validation errors, and saving you reload the page or close YSE and re-launch.  The workflow is now displaying as blank. 



SYMPTOMS

YSE logs the following error:

Error: 2015-Feb-25 09:38:17.902   XAML's Broke: Unable to serialize type 'prairieFyre.CustomControls.ValidationError'.  Verify that the type is public and either has a default constructor or an instance descriptor. ()
 


CAUSE

Validation was missing on a necessary component, resulting in an invalid business object. 



RESOLUTION

This issue is resolved in MiCC Version 7.1.2.1.

If you haver an earlier version of MiCC, you can work around the problem by doing the following:

  1. Import PCI Compliance Workflow as normal.
  2. Resolve Validation Errors and Configure the workflow as normal.
  3. Do not check Validate Workflow on the Canvas - this property should be unchecked/FALSE.
  4. Save the Workflow.
  5. Close the Workflow's Tab.
  6. Open the general Workflow Tab (the one that shows a list of all workflows up top, and details of the selected one below)
  7. Select the Imported Workflow from the list and using the designer docked inside the Tab on the right, set Validate Workflow to checked/TRUE and save it.


APPLIES TO

MiCC 7.1.X.X 

Keywords: PCI compliant system workflow import error blank

Ignite 7.1.2.1 - Known issues

$
0
0
Article ID: 52280 - Last Review: May 11, 2015

INFORMATION

The text editing engine for Ignite was updated in MiCC Version 7.1.2.1, allowing us to introduce a new and improved spell checker.

Below are a list if minor issues thats till exist.

  • Images embedded into a signature do not copy and paste correctly into a message.
  • When pasting a table from Excel into Ignite, formatting (font colors and styles) do not paste.  The actual data remains intact.
  • When trying to move a table by clicking and dragging on the sign, it will create a copy of the table within one of the cells.  Use alignment options instead.
  • When changing from bullet list to numbered, sometimes the first bullet remains and needs to be removed manually.
  • When you correct a word using the spell checker, the cursor jumps to the end of the word.
  • If you modify the FROM field, then insert an image into the body of an email, then start typing in the TO field, the cursor will jump back into the body.
  • You may encounter a script error when attempting to select all (CTRL A) on a template with an image.
  • When inserting a template with a numbered list, if you then convert to a bullet list, the numbers will remain (and need to be manually removed)
  • In an environment where clients have Internet Explorer 9, you may encounter a script error when trying to send email in Ignite.  The new editing engine works best with Internet Explorer 11.
  • When pasting text into Ignite, the spell checker may indicate a word is misspelled if the formatting changes mid-word (text color, etc).


APPLIES TO

Version 7.1.2.1 and newer. 

Keywords: Ignite known issues

MAD0001 - Unable to connect to the maintenance alarm dispatcher

$
0
0
Article ID: 51339 - Last Review: May 12, 2015

DESCRIPTION

This error means that an attempt to connect the maintenance alarm dispatcher failed.  This probably means the dispatcher is not running.  If the dispatcher is running and the error persists, no alarm updates will be processed from the alarm dispatcher.

SEVERITY

Error

IMPACT

In order to raise alarms, services send details to the Maintenance Alarm Dispatcher service.  If they are unable to connect to the Maintenance Alarm Dispatcher, they will not be able to raise alarms.

TROUBLESHOOTING STEPS

  1. Ensure that the maintenance alarm dispatcher is running.
  2. Check the dispatcher logs for errors.
  3. As a last attempt, restart the dispatcher. 


APPLIES TO

CCM 6.X and newer

Keywords: MAD0001

MAD0003 - Unable to find the SNMP memory mapped file

$
0
0
Article ID: 51341 - Last Review: May 12, 2015

DESCRIPTION

This error means that the PF alarm SNMP dll has not been loaded.

SEVERITY

Error

IMPACT

Alarms will not be pushed to your SNMP software until this issue is reoslved.

TROUBLESHOOTING STEPS

  1. Ensure windows SNMP service is installed.
  2. Ensure windows SNMP service is running.
  3. Check the event log for SNMP errors.
  4. In the registry, create DWORD value (32 bit server) HKLM/SOFTWARE/prairieFyre/PfSnmpAgent/[MaxLogsToWrite] = 0xffffffff or (64 bit server) HKLM/SOFTWARE/Wow6432Node/prairieFyre/PfSnmpAgent/[MaxLogsToWrite] = 0xffffffff
  5. Restart the SNMP service, then check %windir%\System32\snmpdbg.log for errors.


APPLIES TO

CCM 6.X and newer

Keywords: MAD0003

6.0 CCM/IQ Application and Service log folder locations

$
0
0
Article ID: 51070 - Last Review: May 15, 2015

SUMMARY

This article contains the folder location (and filename) of each Contact Center Management, Intelligent Queue, and IVR service and application.



CLIENT LOGS

Windows XP/Server 2003 Client Logs

Application/ServiceLog Name
Contact Center ClientC:\Documents and Settings\[Username]\My Documents\CCMLogs\ContactCenterClient.txt
Flexible ReportingC:\Documents and Settings\[Username]\My Documents\CCMLogs\prairieFyre.Reporting_LOG.txt
MiAudio Emulation[InstallDir]:\Program Files\prairieFyre Software Inc\CCM\Services\MiAudioEmulationServer\Logs\MiAudioService.log
Multimedia Outlook Plug-inC:\Documents and Settings\[Username]\Application Data\CyberAED\AEDPlugin.log
SalesForce Browser Connector[InstallDir]:\Program Files\prairieFyre Software Inc\CCM\Applications\SalesforceIntegration\browser_connector.log
SalesForce CTI Connector[InstallDir]:\Program Files\prairieFyre Software Inc\CCM\Applications\SalesforceIntegration\cti_connector.log
Updater Service[InstallDir]:\Program Files\prairieFyre Software Inc\CCM\Logs\UpdaterService.log
Workforce Scheduling (WFS)C:\Documents and Settings\[Username]\My Documents\CCMLogs\CCSClient.log
YourSite ExplorerC:\Documents and Settings\[Username]\My Documents\CCMLogs\YSE.log

Windows Vista/7/Server 2008 Client Logs

Application/ServiceLog Name
Contact Center ClientC:\Users\[Username]\Documents\CCMLogs\ContactCenterClient.txt
Flexible ReportingC:\Users\[Username]\Documents\CCMLogs\prairieFyre.Reporting_LOG.txt
MiAudio Emulation[InstallDir]:\Program Files\prairieFyre Software Inc\CCM\Services\MiAudioEmulationServer\Logs\MiAudioService.log
Multimedia Outlook Plug-inC:\Users\[Username]\AppData\Roaming\CyberAED\AEDPlugin.log
SalesForce Browser Connector[InstallDir]:\Program Files\prairieFyre Software Inc\CCM\Applications\SalesforceIntegration\browser_connector.log
SalesForce CTI Connector[InstallDir]:\Program Files\prairieFyre Software Inc\CCM\Applications\SalesforceIntegration\cti_connector.log
Updater Service[InstallDir]:\Program Files\prairieFyre Software Inc\CCM\Logs\UpdaterService.log
Workforce Scheduling (WFS)C:\Users\[Username]\Documents\CCMLogs\CCSClient.txt
YourSite ExplorerC:\Users\[Username]\Documents\CCMLogs\YSE.txt


SERVER LOGS

Application/ServiceLog Name
.NET Enterprise Server[InstallDir]\prairieFyre Software Inc\CCM\Logs\prairieFyre.Services.EnterpriseServerLog.txt
Auditor[InstallDir]\prairieFyre Software Inc\CCM\Logs\prairieFyre.Services.Auditor.Server.txt
CCS Server (WFS)[InstallDir]\prairieFyre Software Inc\CCM\Logs\CCSServerLog.txt
Collector[InstallDir]\prairieFyre Software Inc\CCM\Logs\CollectorLog.txt
Collector MiTai Apps[InstallDir]\prairieFyre Software Inc\CCM\Logs\Mitel\prairieFyre.Services.Collector\Logs\MitaiApps.log
Config Service[InstallDir]\prairieFyre Software Inc\CCM\Logs\ConfigService.log
Configuration Wizard[InstallDir]\prairieFyre Software Inc\CCM\Logs\ConfigurationWizard_LOG.txt
Data Processor[InstallDir]\prairieFyre Software Inc\CCM\Logs\DataProcessor.log
Data Synchronization[InstallDir]\prairieFyre Software Inc\CCM\Logs\prairieFyre.Services.DataSynchronizationService.log
Exchange Setup(On Exchange Server)   [InstallDir]\prairieFyre Software Inc\CCM\Logs\ExchangeDiagnostics.txt (or MCCExchangeSetup.txt)
Exchange Objects(On Exchange Server)   [InstallDir]\prairieFyre Software Inc\CCM\Services\ExchangeRouter\ExchangeRouter.txt (or MCCExchangeObjects.txt)
IQ Callback[InstallDir]\Mitel Networks\6160\Logs\CallbackEngine.txt
IQ Configuration Manager[InstallDir]\Mitel Networks\6160\Logs\6160IQConfigurationManagerLog.txt
IQ Maintenance[InstallDir]\Mitel Networks\6160\Logs\MaintenanceEngine.txt
IQ Messaging[InstallDir]\Mitel Networks\6160\Logs\MessagingEngine.txt
IQ Music[InstallDir]\Mitel Networks\6160\Logs\MusicEngine.txt
IQ Recording[InstallDir]\Mitel Networks\6160\Logs\RecordingEngine.txt
IQ UPiQ[InstallDir]\Mitel Networks\6160\Logs\UPiQEngine.txt
IVR Inbound(On IVR Server*)   [InstallDir]\prairieFyre Software Inc\CCM\Logs\IvrInboundService.txt
IVR Music(On IVR Server*)   [InstallDir]\prairieFyre Software Inc\CCM\Logs\IvrMusic.txt
IVR Outbound(On IVR Server*)   [InstallDir]\prairieFyre Software Inc\CCM\Logs\IvrOutbound.txt
IVR UPiQ(On IVR Server*)   [InstallDir]\prairieFyre Software Inc\CCM\Logs\IvrUpiqService.txt
Maintenance Alarm Dispatcher[InstallDir]\prairieFyre Software Inc\CCM\Logs\MaintenanceDispatcher.txt
MiTAI Proxy[InstallDir]\prairieFyre Software Inc\CCM\Logs\MiTAIProxyServerLog.txt
MiTAI Proxy MiTai Apps[InstallDir]\prairieFyre Software Inc\CCM\Logs\Mitel\prairieFyre.Services.MitaiProxyServer\Logs\MitaiApps.log
Reporting[InstallDir]\prairieFyre Software Inc\CCM\Logs\Reporting.log
Report Distribution[InstallDir]\prairieFyre Software Inc\CCM\Logs\Reporting - Distribution.log
Server Monitoring Agent[InstallDir]\prairieFyre Software Inc\CCM\Logs\ServerMonitoringAgent.txt
SQL Writer[InstallDir]\prairieFyre Software Inc\CCM\Logs\prairieFyre.Services.SQLWriter.log
Support Packager[InstallDir]\prairieFyre Software Inc\CCM\Logs\SupportPackager.log
WatchDog[InstallDir]\prairieFyre Software Inc\CCM\Logs\WatchDogLogs.txt
Workforce Management[InstallDir]\prairieFyre Software Inc\CCM\Logs\WFMService.log

*IVR Services may be on the Enterprise Server, or a Remote Server.  The logs will exist on the server that controls the IVR Services for you.



APPLIES TO

CCM version 6.X

Keywords: ccm 6110 iq 6160 client server logs location folder file name logging ivr

MAD0002 - Unable to connect to the alarm feed

$
0
0
Article ID: 51340 - Last Review: May 12, 2015

DESCRIPTION

This error means that an attempt to connect to the alarm feed failed.

SEVERITY

Error

IMPACT

The color coded "gumdrop" at the bottom right of YourSite Explorer cannot display the alarm condition of the server.

TROUBLESHOOTING STEPS

  1. Ensure IIS is running.
  2. Ensure that the maintenance alarm dispatcher is running.
  3. Check the dispatcher logs for errors.
  4. Restart the dispatcher service.
  5. Do an IIS reset (Start > Run > type IISRESET). 


APPLIES TO

CCM 6.X and newer

Keywords: MAD0002

How to migrate your database to a new server

$
0
0
Article ID: 51964 - Last Review: May 13, 2015

INFORMATION

When upgrading from a 6.0.X.X environment to 7.0.X.X you may wish to move to a new server as well.  When doing this there are two ways of carrying your configuration over:

  • Using a configuration backup and resummarizing data
  • Migrating your SQL database over

If you have reporting data for a long period already committed to the database, migrating the SQL database as a whole will be more efficient.


PROCESS

1. Ensure that you retain a configuration backup and the \DataDirectory\ folder from the old server, as a redundant backup.
2. Backup the SQL database (CCMData and CCMStatisticalData).
3. Set up the new server hardware and pre-requisite components.
4. Restore the backed up databases to the new server.
5. Run the Atlantic Installation as normal.  The installation process will detect the existing database and update the SQL Schema automatically.

APPLIES TO

7.0 

Keywords: migrate database db ccmdata ccmstatisticaldata atlantic upgrade

HowTo - Disabling Delta Changes (reducing Config Service resource usage, increased network usage)

$
0
0
Article ID: 52282 - Last Review: May 19, 2015

INFORMATION

When committing changes in YourSite Explorer, the Config service pushes these changes to all necessary services and clients.  This can result in the Config service using large amounts of CPU or Memory on your server.

In an environment where this is causing issues, you can disable these delta changes and instead just push the configuration to clients.  This will reduce the resource usage of the Config service at the expense of network bandwidth. 

 

HOW TO

In order to disable delta changes, do the following:

1. On the MiCC server go to [InstallDir]\CCM\Services\ConfigService\ .
2. Open the GlobalAppSettingsEditor.exe .
3. Input the following information:

  • Application:  (leave this blank)
  • SectionGroup: prairieFyre.Configuration.BusinessObjects.Properties.Settings
  • Name: DisableDeltaChanges
  • Value: true
  • Description:  (You can put any note you like here)
  • NOTE: You must enter something in the Description field in order to save.

4. Click Save.  Note that it can take between 30 seconds and 2 minutes to commit these changes.  Wait for the confirmation screen.



APPLIES TO

MiCC version 6.X and 7.X 

Keywords: disable delta changes config service performance CPU memory

Config service reporting OutOfMemory exceptions

$
0
0
Article ID: 51884 - Last Review: May 20, 2015

PROBLEM

Poor performance on the Enterprise Server.  When checking the Config Service log you find references to OutOfMemory exceptions. 



CAUSE

On busy sites the DeleteTracking table in SQL can grow quite large, and the Config service keeps some of it in memory after each Maintenance runs.



RESOLUTION

There are two steps to resolving this issue:

1. Setting the DeleteTracking cleanup interval in SQL.

  • Open SQL Management Studio.
  • Expand CCMData.
  • Expand Tables.
  • Find the dbo.tblEnterpriseConfig_Enterprise table.  Right-click and select Edit top 200 rows.
  • Scroll to the right and ensure that DeleteTrackingCleanupInDays is set to 1.
  • Close SQL Management Studio.

 

2. Modify the service configuration file.
  • Go to the [INSTALL DIRECTORY]\CCM\Services\MaintenanceAlarmDispatcher\ folder.
  • Open the MaintenanceTasks.config file in notepad.
  • By default it will look like the following:

  • You will need to comment out the <add key="DayOfMonth" value="1" /> entry by adding  <!-- to the beginning and --> to the end (see image below).
  • Modify the <!--<add key="DayOfWeek" ... entry so that it shows <add key="DayOfWeek" value="Everyday" /> (see image below).



3. Purge the content of the tblConfig_DeleteTracking table in SQL.

  • Launch SQL Studio Management.
  • Create a new query.
  • In the Query Editor, type in the following query;



  • Click on Execute.
  • Upon completion, the table will be clear of its content.

This will increase the frequency of the maintenance task to purge your DeleteTracking table and will now be purged on a daily basis on items older than 1 full day.


APPLIES TO

CCM 6.0 and newer 

Keywords: DeleteTracking config service OutOfMemory exception maintenance

5.10.7.0 / 7.1.2.0 - When registering an IVR Endpoint to an SBS/SBA you cannot transfer calls to any Internal/External destination

$
0
0
Article ID: 52256 - Last Review: May 22, 2015

PROBLEM

When registering an IVR Endpoint to an SBS/SBA you cannot transfer calls to any Internal/External destination. 

This issue is present when running MiContact Center for Microsoft Lync 5.10.7.0 alongside IVR 7.1.2.0.


RESOLUTION

On the all IVR servers, you will need to add a manual configuration. 
1. Go to [InstallDir]\CCM\Services\RoutingMediaService\.
2. Open the RoutingMediaService.exe.config file in an editor such as Notepad.
3. Find the <Mitel.Ucma.Properties.Settings>section.
4. Add the following, and put your domain in the string section:

     <setting name="TrustedServers" serializeAs="Xml">
          <value>
               <ArrayOfString xmlns:xsi="
http://www.w3.org/2001/XMLSchema-instance"
               xmlns:xsd="
http://www.w3.org/2001/XMLSchema">
                    <string>YOUR SBA FQDN HERE<string>
               </ArrayOfString>
          </value>
     </setting>

5. Save the file.
6. Restart the RoutingMedia service.

APPLIES TO

MiCC4Lync 5.10.7.0 with IVR 7.1.2.0 

Keywords: sbs sba ivr endpoint internal external transfer

IVQ does not show calls that abandon while ringing on an agent, only those that abandon in queue

$
0
0
Article ID: 52284 - Last Review: May 25, 2015



PROBLEM

In CCC, the IVQ Monitor Abandoned Media section shows a lower number of calls than the Queue Now Monitor Abandoned Calls column.



CAUSE

Calls which terminate when the caller hangs up while the call is ringing at an agent station will NOT peg as Abandoned in the IVQ Abandoned Media grid, but may peg in the Abandon column of the Queue Now Monitor (provided the total call duration is greater than the short abandon cutoff).

This disparity is because the IVQ monitor is built on the Mitai data stream, and the Queue Now Monitor is built on the SMDR data stream. The Mitai data stream interprets calls that are ringing at an agent station as out of the queue, and therefore does not report calls that abandon while ringing at an agent station as abandons for the queue. The SMDR data stream, on the other hand, interprets the call as being in the queue until the moment the agent actually picks up, so it does report calls that abandon while ringing at the agent station as abandons for the queue.



SUMMARY – Which Monitor / Report Shows What:

Queue Now Monitor Abandon column shows:

  • Abandoned calls that abandoned while hearing the queue RADs or hold music, which were in the queue for longer than the short abandon threshold* for the queue.
  • Abandoned calls that abandoned while ringing at an agent station, whose combined time in the queue and ringing at the agent was longer than the short abandon threshold* for the queue.

 

Queue Now Monitor Short Abandon column shows:

  • Abandoned calls that abandoned while hearing the queue RADs or hold music, which were in the queue for less time than the short abandon threshold* for the queue.
  • Abandoned calls that abandoned while ringing at an agent station, whose combined time in the queue and ringing at the agent was less than the short abandon threshold* for the queue.

 

The IVQ Abandoned Media grid shows:

  • The IVQ Monitor calls abandoned when they were in the queue, regardless of how long they were in queue; but NOT calls that were abandoned while ringing at an agent station.

 

The Queue Unavailable Trace report shows:

  • All calls that abandoned while in queue or while ringing at an agent station.

*The Short Abandon Threshold is set in the queue properties in YourSite Explorer > Queues. The default value is 6 seconds.



CONFIRMING THIS IS WHAT’S HAPPENING

You can confirm that calls are abandoning while ringing at agent stations this way:

1. From CCMWeb > Reporting > Queue Reports, run a Queue Unavailable Trace report against the queue for the period in question. On the report, look for Abandoned calls, and note the time of abandon for one or several of the calls.

(The Queue Unavailable Trace report will show absolutely all abandoned calls, regardless of whether they were short abandons [by default, a short abandon is a call that abandons after 6 seconds or less] or regular abandons, and regardless of whether they abandoned while in the queue [the part of the call where you hear "Your call is important to us" and then the hold music] or while ringing at an agent station.)

2. Find these calls in the ACD Inspector.

a. Open CCC with an account that has the right to view the Data Inspectors. (_admin will usually have this right.)

b. Click on the Tools tab at the top of CCC, and choose “Inspectors”.

c. The “Data Inspectors” window will open. At the top of this window, choose “ACD Inspector”.

d. Click “Select Dates” (near the top-left” and choose the date in question.

e. In the “Select media servers” section, choose the media server(s) on which the ACD agents reside.

f. Click “Start Search”.

g. In the search results window, click on the drop-down arrow beside the column heading “Function/Event”, and choose “Agent Ringing ACD”.

h. Look for an Agent Ringing ACD event that is either at the exact time as your chosen abandoned call, or immediately before. Note the value in the Agent ID column.

i. Click on the drop-down arrow beside the column heading “Agent ID”, and choose the Agent ID from part h.

j. Now, click on the drop-down arrow beside the column heading “Function/Event”, and choose “Agent Answer ACD”.

If there is no Agent Answer ACD event to correspond with the Agent Ringing event (i.e. no Agent Answer ACD event that is at the same time or within one or two seconds of the Agent Ringing Event), the caller abandoned while the call was ringing at the agent station. This would result in an abandon being recorded in the Queue Now monitor (either in the Short Abandon column, or the Abandon column, depending on the total combined amount of time the call was in the queue and ringing at the station).

If there is an agent answer event, please go back to the Queue Unavailable Trace report and choose another abandoned call.



APPLIES TO

CCM all versions

Keywords: IVQ Abandon Abandoned Queue Now Disparity Count Counts

HotFix KB180815 - Report emailing functionality intermittently failing without error

$
0
0
Article ID: 52286 - Last Review: , 2015

PROBLEM

Intermittently reports weren't emailing out. 



RESOLUTION

This HotFix must be installed onto MiCC Version 6.0.3.0.

1. Download the attached KB180815.EXE to the MiCC server. 

2. Double-click the KB180815.EXE file and follow the on-screen prompts.

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



APPLIES TO

6.0.3.0 

Keywords: 180815 KB180815 report reports email emailing distribution fail failing

HotFix KB254986 - IVR Ports failing with Out Of Memory exception

$
0
0
Article ID: 52285 - Last Review: May 25, 2015

PROBLEM

IVR ports are becoming unresponsive.  Logging indicates an Out Of Memory exception. 



SYMPTOMS

In the IVR port log you will see an error like the following:

Error: 27/04/2015 07:41:08 [8089646-10.47.35.99] - ERROR - Exception:System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
at System.Text.StringBuilder.ToString()
at System.IO.BinaryReader.ReadString()
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadObjectString(BinaryHeaderEnum binaryHeaderEnum)
at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run()
at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, Boolean isCrossAppDomain, IMethodCallMessage methodCallMessage)
at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream)
at System.Workflow.ComponentModel.Activity.Load(Stream stream, Activity outerActivity, IFormatter formatter)
at System.Workflow.ComponentModel.Activity.Clone()
at System.Workflow.Runtime.WorkflowExecutor.GetWorkflowDefinitionClone(String workflowContext)
at System.Workflow.Runtime.WorkflowInstance.GetWorkflowDefinition()
at prairieFyre.Ivr.Workflow.WorkflowHelper.UpdateExecutionAlarm(WorkflowInstance aInstance, Boolean aFailedToExecute) in e:\TeamBuild\CCS\6.0.3.0_IVR\Sources\Source\prairieFyre\Workflow\Common\WorkflowHelper.cs:line 316
at prairieFyre.Ivr.Workflow.WorkflowHelper.ExecuteWorkflow(WorkflowRuntime runtime, WorkflowInstance instanceToStart) in e:\TeamBuild\CCS\6.0.3.0_IVR\Sources\Source\prairieFyre\Workflow\Common\WorkflowHelper.cs:line 306
at prairieFyre.Ivr.Workflow.Telephony.WFPortCallflowExecutor.ExecuteWorkflowInstance(WorkflowInstance instanceToExecute) in e:\TeamBuild\CCS\6.0.3.0_IVR\Sources\Source\prairieFyre\Workflow\Common\Telephony\WFPortCallflowExecutor.cs:line 279
at prairieFyre.Ivr.Workflow.Telephony.WFPortCallflowExecutor.Start(DispatcherEventArgs args) in e:\TeamBuild\CCS\6.0.3.0_IVR\Sources\Source\prairieFyre\Workflow\Common\Telephony\WFPortCallflowExecutor.cs:line 199
at prairieFyre.Workflow.Telephony.WFInboundPort.OnStartWorkflowEvent(Object sender, DispatcherEventArgs args) in e:\TeamBuild\CCS\6.0.3.0_IVR\Sources\Source\prairieFyre\Workflow\Common\Telephony\WFInboundPort.cs:line 196 (8089646 - 10.235.0.105)

 



RESOLUTION

This HotFix must be installed onto MiCC Version 6.0.3.0 with a number of existing HotFixes already installed. 

Install the following HotFixes in this order:
1. KB175546
2. KB176574
3. KB176785
4. KB179467
5. KB180093
6. KB180791
7. KB180815
8. KB211529
9. KB217690

Once you have done this.

1. Download the attached KB254986.EXE file to the MiCC server.
2. Double-click the KB254986.EXE file and follow the on-screen prompts.

NOTE: Installing each HotFix will restart the prairieFyre services.  In order to avoid service interruption we recommend applying these patches after hours or during a scheduled maintenance window.




APPLIES TO

IVR 6.0.3.0 

Keywords: IVR port ports out of memory outofmemory


MCC Agent Priority / Preferred Agent Option

$
0
0
Article ID: 50434 - Last Review: May 25, 2015

Multimedia Preferred Agent is a feature by which a Multimedia email from customer X (identified by his/her email address) would be routed to the last agent who handled the last message from that same customer. By default, this feature is turned off. It is turned on by setting a column value in the prairieFyre SQL database to an integer greater than zero. The value is in minutes and it denotes the amount of time the message remains tentatively assigned to the agent while he or she remains unavailable. Once this threshold is exceeded, the message is offered to the longest idle agent.



MORE INFORMATION

Step 1: Turn on MCC Preferred Agent in SQL

  1. Launch SQL Server Management Studio
  2. Connect to the CCM datasource
  3. Expand Databases=>CCMData
  4. Open the respective table you wish to modify:

    Email: tblConfig_Attributes_Exchange_Queue
    Fax:   tblConfig_Attributes_Fax_Queue
    Chat: tblConfig_Attributes_Chat_Queue

  5. Change the NonAvailableRequeueTime column to a time in minutes (Ex. 2)

Step 2: Notify 6150 of this change

After setting the value, the prairieFyre .NET Enterprise Server service needs to be notified of this change. You can either issue a dummy save from the CCMWeb to trigger a reload (Recommended) or you can restart the service.


APPLIES TO

prairieFyre Version 6.X and earlier

Detailed Release Notes: 7.1.2.1

$
0
0
Article ID:  - Last Review: May 25, 2015

INFORMATION

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


APPLIES TO

7.1.2.1 

Keywords: DRN release notes 7.1.2.1

Agent Idle time resets to zero if the Agent makes an Outbound Call or receives a non-ACD call.

$
0
0
Article ID: 50021 - Last Review: September 17, 2013

PROBLEM

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



SYMPTOMS

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




RESOLUTION

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

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

  • ApplicationName: leave this field blank.
  • SectionGroup: This should be prairieFyre.BAL.DataAnalysis.Properties.Settings , note that it is case sensitive.
  • Name: This will be CalculateLastACDIdleFromLastACD , note that this is case sensitive.
  • Value: This should be 1 to enable the feature (0 if you wanted to disable it again).
  • Description: Add a note as to why you are adding the feature.  Note that you must have something in this field.
3. Click Save
4. It can take up to a minute for the changes to complete.  Wait for the notification that it is saved.
5. Restart the .NET Enterprise Server service.
6. Close and re-launch your Contact Center Client to see the changes.

APPLIES TO

CCM 6.0.2.X 

Keywords: Agent Idle time reset non-acd outbound

Agent Group Presence changes not displaying in Contact Center Client

$
0
0
Article ID: 52289 - Last Review: May 25, 2015

PROBLEM

After a supervisor changes an agent's Group Presence settings using the right-click menu in an Agent State monitor, they open the Join/Leave Group screen again and the changes are not reflected. 



SYMPTOMS

No error message is thrown, but the change is not reflected if you re-open the Join/Leave Group window. 



RESOLUTION

There is a manual configuration to automatically query group presence after a command is issued.  To implement this:


1. On the MiCC server go to [InstallDir]\CCM\Services\ConfigService\ .
2. Open the GlobalAppSettingsEditor.exe .
3. Fill in the following information:
  • Application: (leave this blank)
  • SectionGroup: appSettings
  • Name: QueryPresenceAfterCommand
  • Value: True
  • Description: (you may enter anything you like here)
NOTE: You must enter something in the Description cell in order to save.
4. Click Save. It may take 30 to 60 seconds to complete the save.  Please wait for the confirmation window.
5. Go to the Services control panel.
6. Restart the prairieFyre Collector Service (v5).



APPLIES TO

MiCC 7.1.2.0 and newer 

Keywords: AGP group presence change contact center client CCC failing

How to Test SMTP Settings Using Telnet

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

WHEN TO USE THIS PROCEDURE

This procedure can be useful when the YourSite Explorer > Mail Servers > Test Mail Server button is returning a failure result, and you need to work out whether this is because of a problem with the settings being entered (as opposed to a problem in the CCM software).



LIMITATIONS

1. This procedure will not allow you to rule out problems that are caused by the mail server selectively screening out emails with Excel documents attached, or alarm emails from Contact Center Client.

2. Additional steps not recorded in this article will be needed to test mail servers which have:

  • TLS (includes smtp.gmail.com)
  • SSL
  • Required authentication (that is, mail servers which are not open relay)


TESTING SMTP SETUP USING TELNET

Important Note:

When testing SMTP, it is very important to know that you cannot use backspace with SMTP commands.

If you press backspace once you’ve opened a Telnet session to the SMTP port, your cursor will move back and allow you to (seemingly) overwrite what you typed before, but you will get errors and unpredictable results from the command.

Instead, please type carefully, and, if you make a mistake, you may need start over with a new Telnet session.



To test:

1.  In the command prompt, type:    telnet [mail server FQDN or IP] [mail server port]
e.g. telnet 10.22.256.11 25 , or
    telnet smtp.mitel.com 25

If the command is successful, you will see something like this:

server: 220 10.22.256.10 ESMTP server ready Tue, 20 Jan 2014 22:33:36 0200
(If the command fails because Telnet is not installed, go to Server Management > Roles and Features > Features, and install the Telnet Client feature.)


2. Carefully, without using backspace, type this:
HELO mycomputername.mydomain.com

…where mycomputername.mydomain.com is the name of the computer from which you’re doing the test (i.e. the CCM server)

If the HELO command was successful, you will see this:
250 mx1.example.com

3. Carefully type this:
MAIL from: senderUsedinCCM@thedomain.com
You should get this reply:
250 Sender senderUsedinCCM@thedomain.com Ok

4. Type:
RCPT to: youremail@youremaildomain.com
You should get this reply:
250 Recipient youremail@youremail.com Ok

5. Type:
DATA
You should get this reply:
354 Ok Send data ending with <CRLF>.<CRLF>
6. Type this:
From: senderUsedinCCM@thedomain.com
To: recipientsemail@whatever.com
Subject: SMTP Test message
Body text goes here - This is a test message.
.
(The period, all alone on its own line, signals to the SMTP server that you’re done adding body text.)

You should get this reply:
250 Message received:

7. Type:
QUIT

If you have not gotten an error in this process, the mail server has accepted the message, validating that the mail server settings entered in YSE are valid.


APPLIES TO

CCM - All versions


Keywords:
port 25 SMTP helo telnet test mail settings mail server
Viewing all 959 articles
Browse latest View live


Latest Images