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

Account and classification codes are not displaying in Desktop or Web ignite

$
0
0
Article ID: 52523 - Last Review: January 31, 2017

PROBLEM

Account and classification codes are not displaying in Desktop or Web ignite. 



CAUSE

Account Code categories have been enabled and Ignite does not support this view. 



RESOLUTION

1. Log into Yoursite Explorer as a System Administrator
2. In the DEVICES pane, select Account Codes
3. On the Yoursite Explorer menu bar at the top of the screen, click the Configuration tab
4. After clicking configuration, on the right hand side of the top bar menu, uncheck Enable Account Code Categories
NOTE: (Code Categories are only supporting in Contact Center Client)
5. Save.  Close and re-launch Ignite, Account and Classification codes will now be available for use in Ignite. 
 



APPLIES TO

MiCC 7.X and newer 

Keywords: classification account code codes ignite categories


License Violation due to App Conn license

$
0
0
Article ID: 52524 - Last Review: February 6, 2017

INFORMATION

On January 31, 2017 Mitel removed the Application Connection license from all MiContact Center licensing.  While Mitel used to include Application Connection licenses for MiCollab UM to allow Mitel Partners to program the ports on the MiVoice Business, the ports are now programmed as a ‘Trusted Service’ on the MiVoice Business, and as such Application Connection licenses are no longer required.  You cannot use Trusted Services to build ACD Hot Desk extensions, or extensions of any kind.

The only application that still requires Application Connection licenses is MiCollab AWV (Audio/Web/Video).  The Audio ports are programmed on the MiVoice Business as Generic SIP Devices and therefore require the Application Connection license to allow that programming.  The Application Connection licenses were not included in the MiCC AMC bundles for use with AWV as MiCC AMC bundles do not include AWV licensing.

UCC Standard and Premium licenses include these Application Connection licenses for the audio ports, since AWV ports with HD codec are provided with these UCC licenses.

IMPORTANT: If any customer re-purposed the Application Connection licenses included with MiContact Center for use as ACD hot desk extensions, upon sync of the MiVB after this update, will immediately be in license violation. 

As communicated in Product Bulletin PB 20150541, customers were advised that

The previous requirement of one MiVoice Business user license per MiContact Center agent licenses still remains. If upon upgrading to Release 8.0 a customer does not have sufficient MiVoice Business user licenses to meet the needs of the agents using concurrent user licenses, you must contact your Mitel sales representative to purchase the proper number of user licenses.

Product Bulletin PA20160005 communicates this information as well;



If you leveraged these Application Connection Licenses to license ACD hot desk extensions and are now experiencing a license violation, you will need to purchase one of the following part numbers to remain compliant:

If the MiVoice Business is Standalone base software, you will need to purchase part number 54004976 - Standard User license x1 for each

If the MiVoice Business is Enterprise base software, you will need to purchase part number part number 54004975 - Enterprise User license. 

Note:  In USA, new sales are all Enterprise. 
Canada and Latin America can still sell Standalone.

If you need assistance with understanding the license violation timing, please contact AMC_Accounts@Mitel.com for support.


 

APPLIES TO

MiCC, all versions 

Keywords: license violation march

HowTo - Make a Client Update Package to be deployed manually

$
0
0
Article ID: 52010 - Last Review: February 7, 2017

PROBLEM

When applying an update to the Enterprise Server that includes adjustments to the Client software, the server will (by default) try to push the updated client software to all client computers.  In environments with large numbers of client computers, or a network bottleneck between the server and clients (such as a WAN connection to another site) this can cause the network connection to become saturated.

For more information on the auto-update process, please see the System Engineering Guide (pg 53 in the current 6.0.2 guide).


ALTERNATE SOLUTIONS

1. The first alternate solution when auto-updating fails is to perform a manual update by copying the needed files to each client computer (Details can be found here).  This is an easy process, but labor intensive.  Only recommended in cases where network security or serious network bottlenecks are preventing updates to a small number of client computers. 

2. For larger deployments it is possible to package the updated client software into a self-extracting archive which you can stage on the section of network needed, and execute using an administrative function.  As you want this updater to run before any of the client software has launched, we recommend pushing the update as part of a logon script, or after hours.  For instructions on creating this Update Package, see below.


CREATING AN UPDATE PACKAGE

1. Install the service pack/fix pack on the CCM server
2. Create a folder structure which looks like this:
    PFYRECCP
                Applications
                Services

3. If you go to [InstallDir]\CCM\Applications\ on the sever, you will find a folder with each of the following names. Copy these folders into \PFYRECCP\Applications\.
    CCMWebStub
    CcsClient
    ContactCenterClient

    EmployeePortalStub
    FlexibleReporting
    Ignite
    MbgConnector
    OutlookPlugin
    SalesforceIntegration
    YSE

4. Next, copy from [InstallDir]\CCM\Services\ the folder named UpdaterService and MiAudioEmulationServer into \PFYRECCP\Services\ .
5. You should now have the following folder structure:
    PFYRECCP
        Applications
            CCMWebStub
            CcsClient
            ClientRole
            ContactCenterClient

            EmployeePortalStub
            FlexibleReporting
            Ignite
            MbgConnector
            OutlookPlugin
            SalesforceIntegration
            YSE
        Services
            UpdaterService
            MiAudioEmulationServer

5. Create a batch file called setup.bat .  The default configuration for a 32bit client is as follows:

net stop "updaterservice"
net stop "miaudioservice"

xcopy %TEMP%\PFYRECCP "%PROGRAMFILES%\PrairieFyre Software Inc\CCM" /s /c /h /e /r /k /y

net start "updaterservice"
net start "miaudioservice"

NOTE: There are a few considerations in how you create this batch file.

  • If your clients have their Updater Service disabled already, you can remove the net stop and net start commands for updaterservice.
  • The destination path may not be exactly as above.  %PROGRAMFILES% will always take you to the \Program Files\ folder, however on a 64 bit client we want to install into \Program Files (x86)\ instead.  The variable for this is %PROGRAMFILES(X86)%.
  • If you have a mix of 32 and 64 bit client computers, this adds some confusion.  You can either duplicate the XCOPY line into both locations (thus doubling the space used on the client computers), or you can create two separate packages for deployment (your administrative action will need to distinguish)
  • In MiContact Center Verison 8.X a new install of the software will install to %PROGRAMFILES(X86)%\Mitel\MiContact Center\ instead.  Check the installed path and adjust accordingly. 

6. Copy the batch file into the root of the \PFYRECCP\ folder
7. Ensure that you have WinRAR installed on the server (you may be able to use other archiving tools, but the configuration below will need to be adjusted accordingly).
8. Right-click the \PFYRECCP\ folder and Add to Archive.
9. Check Create SFX Archive.
10. Click the Advanced tab at the top, then click SFX Options.
11. In the General tab, Path to Extract field input %TEMP% .
12. Click the Setup tab.  In Run after extraction input %TEMP%\PFYRECCP\Setup.bat .
13. Click the Update tab.  Under Overwrite mode select Overwrite all files .
14. Click OK.
15. Click the Comment tab at the top.
16. In here is a section to Enter a comment manually which will have the following auto-populated:

;The comment below contains SFX script commands

Path=%TEMP%
Setup=%TEMP%\PFYRECCP\Setup.bat
Overwrite=1

17. Add a new line below Overwrite=1 that says Silent=1 .  It should now look like the following:

;The comment below contains SFX script commands

Path=%TEMP%
Setup=%TEMP%\PFYRECCP\Setup.bat
Overwrite=1
Silent=1

18. Click OK.

19. Deploy the PFYRECCP.EXE file using your administrative tools.  Note that it must be run while none of the software being updated is active.  Deploying as part of a login script is recommended.

NOTE: Although the archive unpacks silently, the batch file does not.  Users will see a command prompt pop up, a list of files fly by, and then the command prompt will close when it’s finished.  The process is complete as soon as the command prompt closes.



APPLIES TO

MiCC, 7.X

Keywords: manual update client component pack administrative package howto how to

How to drop and rebuild the prairieFyre database once SQL Express has reached its 10 GB limit

$
0
0
Article ID: 50258 - Last Review: February 16, 2017

INTRODUCTION

This article describes the steps to drop and rebuild the database once SQL Express has reached its size limit of 10 GB



SUMMARY

SQL Express, unlike full SQL, has a database limit of 10 GB.  Once a database in SQL Express has reached 10 GB in size, no further data can be written into it.  At this time customers will encounter problems logging into the CCM website and are unable to run reports.  Follow the steps below to drop the existing database to create a new one.

NOTE:  It may be more time efficient to try our Data Purge Tool first before dropping and rebuilding the database.



INSTRUCTIONS

Create a backup of the .xml database

  1. Launch Contact Center Client (CCC)
  2. Click on Management in the top left corner
  3. Select Configuration
  4. Select Backup/Restore configuration data
  5. Select Back up and save .xml file to Desktop

Drop the Existing Database

For a video tutorial see here
  1. Launch SQL Server Management Studio
  2. Connect to the local instance of SQLExpress
  3. Expand Databases to see CCMData
  4. Right-click CCMData and select Tasks then Detach
  5. Add check-mark to Drop Database and Close Existing Connections
  6. Right-click CCMStatisticalData and select Tasks then Detach
  7. Add check-mark to Drop Database and Close Existing Connections
  8. Click OK

    Browse to the database storage directory (Defaulted to <Install Dir>\Program Files\PrairieFyre Software inc\CCM\Database\ and move the CCMData.mdf, CCMData.ldf, CCMStatisticalData.mdf, and CCMStatisticalData.ldf files into another directory for safe keeping.

Re-create a New Database

  1. Run Contact Center Management Configuration Wizard (MiCC Setup > Repair in versions 8.x)
  2. Click Next and let the Wizard run though
  3. The Wizard will re-create a blank new CCMData database
  4. Re-launch Contact Center Client (CCC); the database has just been reset, so you will need to log in with the default username and password listed in the User Guide
  5. Click on Management in the top left corner
  6. Select Configuration
  7. Select Back up/Restore configuration data
  8. Select Restore and browse to .xml file on Desktop

Re-Summarize Recent Historical Data Back Into SQL

  1. Launch Contact Center Client (CCC)
  2. Click on Management in the top left corner
  3. Select Maintenance
  4. Select Summarize Data
  5. Under Data Range specify the range for which historical reports are needed
  6. Click Next


APPLIES TO

MiCC/CA/BR


KEYWORDS

SQL drop database

HotFix KB377880 - Multitenant - Employees were able to see some items from other sites

Next: MiCloud Business Partner Built MiCC Deployment Best Practices
Previous: How to drop and rebuild the prairieFyre database once SQL Express has reached its 10 GB limit
$
0
0
Article ID: 52525 - Last Review: February 21, 2017

PROBLEM

Devices from one Site in the configuration were visible to employees of a different Site.



RESOLUTION

This HotFix is to be installed onto MiContact Center Version 8.1.0.0. This hotfix is for Multitenant configured sites only.

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

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

APPLIES TO

MiContact Center 8.1.0.0. 

Keywords: 377880 KB377880 multitenant visible site hotfix

MiCloud Business Partner Built MiCC Deployment Best Practices

Next: Licensing - March 17th expiry for Subscription Timer
Previous: HotFix KB377880 - Multitenant - Employees were able to see some items from other sites
$
0
0
Article ID:  - Last Review: February 22, 2017

INFORMATION

When deploying MiContact Center in a MiCloud Business partner built environment, it is important to follow the appropriate best practices.  Failure to comply with the best practices will prevent automated usage reports from being generated and your operations will have to manually supply usage information for monthly billing.  Specifically, when adding additional systems and/or virtual instances to support additional customers then the following must be observed: 
 
For Virtual Machine deployments:

  • Do NOT clone the virtual image if you already have installed MiContact Center Business on the server and SQL server is also running locally on the same server.
  • Do NOT install\use the MiCC 7.1 OVA. An 8.1.1.0 OVA available and that is what everyone should be using as it does not ship with a database already created.

 
For Physical Machine OR Virtual Machine case:

  • Do NOT restore the same MiCC backup onto another system for two different customers.

 
With the introduction of automated service provider service usage reporting for MiCC, failure to follow these best practices will result in inaccurate usage reports.   The automated service usage reporting relies on unique identifiers in the CCMData database and cloning or restoring databases results in the creation of non-unique identifiers.
 
If these practices have not been followed for existing deployed systems, then please contact Mitel Product Support so that we can identify corrective measures that can be taken to re-establish unique identifiers and ensure the service usage reports are being accurately generated.
 

APPLIES TO

MiContact Center Version 8 or newer 

Keywords: micloud multitenant best practices

Licensing - March 17th expiry for Subscription Timer

Next: Excessive number of short abandons pegging in VWM environment
Previous: MiCloud Business Partner Built MiCC Deployment Best Practices
$
0
0
Article ID: 52527 - Last Review: February 22, 2017

PROBLEM

Sites which updated their licensing between July 19th, 2016 and January 19th, 2017 had a subscription expiry applied in error.

If you allow the subscription to expire on March 17th, without updating your license you may experience the following:

In MiContact Center Version 7.X or older...

  • The Update License button will be removed from the Mitel Contact Center Management Licensing Tool.
  • You will receive a warning that your Demo License has expired.
  • Users will not be able to log into client applications.
  • Outbound workflows will not function.
  • Your licensing will revert to 1 voice media server, 75 voice licenses, 1 premium supervisor, Business Reporter, Call Accounting, and 50 extensions.
In MiContact Center Version 8.X or newer...

  • The License Key is no longer remembered by the MiCC Setup wizard.
  • You will receive a warning that your Demo License has expired.
  • Users will not be able to log into client applications.
  • Outbound workflows will not function.
  • Your licensing will revert to 1 voice media server, 75 voice licenses, 1 premium supervisor, Business Reporter, Call Accounting, and 50 extensions.


SYMPTOMS

Sites will be affected if, during the above time period, they performed any of the following actions:

  • Renewed their Software Assurance
  • Added new Part Numbers to their license
  • Upgraded their version of MiContact Center
  • Requested a new Desaware key
  • Installed a new system 


RESOLUTION

Before March 17th:

In MiContact Center Version 7.X or older...
1. Launch the Mitel Contact Center Management Licensing Tool.
2. Click Update License.
NOTE: If you do not have an internet connection to complete this action, you will need to save a copy of your CCMv5.dlsc file and manually sign it through AMC.

In MiContact Center Verison 8.X or newer...
1. Launch MiCC Setup.
2. Click Update License.
NOTE: If you do not have an internet connection to complete this action, you will need to save a copy of your CCMv5.dlsc file and manually sign it through AMC.

After March 17th:

In MiContact Center Version 7.X or older...
1. Launch the Mitel Contact Center Management Licensing Tool.
2. Click Register Online.
3. You will need to input your Desaware License Key.
4. Click Register.
NOTE: If you do not have an internet connection to complete this action, you will need to save a copy of your CCMv5.dlsc file and manually sign it through AMC.

In MiContact Center Verison 8.X or newer...
1. Launch MiCC Setup.
2. Click Update License.
3. You will need to input your Desaware License Key.
4. Click Next and follow the on-screen prompts.
NOTE: If you do not have an internet connection to complete this action, you will need to save a copy of your CCMv5.dlsc file and manually sign it through AMC.




APPLIES TO

MiCC, all versions 

Keywords: licensing demo license expired subscription timer

Excessive number of short abandons pegging in VWM environment

Next: HowTo - Update licensing or check subscription timers
Previous: Licensing - March 17th expiry for Subscription Timer
$
0
0
Article ID: 51624 - Last Review: April 8, 2015

PROBLEM

In some cases short abandons (roughly 3 seconds in length) are generated for calls that are being routed through IVR. 

 

WORKAROUND

NOTE: Depending the version of IVR you are running, the workaround is very different.

IVR Version 8.X.X.X

1. On the MiCC server, go to [InstallDir]\Services\ConfigService\ .
2. Launch the GlobalAppSettingsEditor.exe.
3. Fill in the following information:

  • Application: DataService.exe
  • SectionGroup: prairieFyre.BAL.DataAnalysis.Properties.Settings
  • Name: HandleInternalAbandonAcdWithFullDigitsDialedAsAnswered
  • Value: true
  • Description: Short Abandons in IVR (You can enter anything you wish in Description, but there must be a value here in order to save)

4. Click Save.  Note that this can take up to two minutes to complete.  Wait for the confirmation screen.
5. In the Contact Center Client you can now re-summarize the data that previously was pegging excessive short abandons, and all data moving forward will be correct.


IVR Version 7.X.X.X

1. On the MiCC server, go to [InstallDir]\CCM\Services\ConfigService\ .
2. Launch the GlobalAppSettingsEditor.exe.
3. Fill in the following information:

  • Application: Leave this field blank
  • SectionGroup: prairieFyre.BAL.DataAnalysis.Properties.Settings
  • Name: HandleInternalAbandonAcdWithFullDigitsDialedAsAnswered
  • Value: true
  • Description: Short Abandons in IVR (You can enter anything you wish in Description, but there must be a value here in order to save)

4. Click Save.  Note that this can take up to two minutes to complete.  Wait for the confirmation screen.
5. In the Contact Center Client you can now re-summarize the data that previously was pegging excessive short abandons, and all data moving forward will be correct.


IVR Version 6.0.X.X

You can prevent the system from generating these short abandons by ensuring that IVR transfers calls to a path before an agent is rung.

1. Create and agent group with no agents in it.
2. Enable the "Queue Calls To group When No Local Agents Are Logged In and Present" option on this group.
3. Set this empty group as the first group in the path.
4. Set a short overflow time on this empty group (2 seconds should be enough)
5. Set a second group, with the answering agents in it to be the second group. 


APPLIES TO

IVR/VWM all versions

Keywords: short abandon vwm ivr


HowTo - Update licensing or check subscription timers

Next: HowTo - SMDR Reorder Buffer for Data Summarization
Previous: Excessive number of short abandons pegging in VWM environment
$
0
0
Article ID: 52528 - Last Review: February 28, 2017

INFORMATION

If you are concerned that you may be affected by the March 17th Subscription Timer, or need to update your licensing, please see the attached document. 

 

APPLIES TO

MiCC, all versions 

Keywords: update license march subscription timer expired

HowTo - SMDR Reorder Buffer for Data Summarization

Next: License not converted when changing from 7.X (or older) to 8.1 (or newer) in AMC.
Previous: HowTo - Update licensing or check subscription timers
$
0
0
Article ID: 52200 - Last Review: March 1, 2017

INFORMATION

This article describes the SMDR Reorder Buffer configuration available in MiContact Center.

SMDRReorderBufferReleaseIntervalInSeconds:  This configuration variable was designed for linking SMDR events together to give a more accurate statistical value.

During Realtime: By Default, this value is 5 seconds.
During Resummarization: By Default, this value is 20 minutes. (20 minutes * 60 seconds = 1200 seconds)

The reason for the different values is that the Statistical Engine will wait for the configuration time before performing the calculations necessary for the statistics it needs to update.  This allows us to check in the past during a small window and double check certain conditions to make sure that the pegging is accurate.

For Realtime, the value is small to allow the statistics to update within 5 seconds of a call being finished.  You can see this delay if you perform your own test call.  Regardless of Abandoning, Answering, etc, watch the Queue Now monitor where the Call went and once the call is completed, sometime shortly after the 5 seconds have past, your Queue Now will update accordingly.  This is due to the SMDRReorderBufferReleaseIntervalInSeconds being 5 seconds, the system waited 5 seconds for anything else and then calculated the appropriate peg.
 
Nightly/Manual Summarization is less of a concern, this is why you can see slight differences between the values you see during the day and the values in the reports the next day, (or after a manual summary is performed)
20 minutes was determined many years ago to be a decent average call length.  It has been increased by other customers due to longer average call times and it can be a benefit to do so if you know you have calls longer than 20 minutes on average.

Increasing the value does increase memory usage of the Data Processor as the Service will hold the events in memory longer before processing the statistics and flushing them out.  Be wary of setting the value to 24 hours (24 hours * 60 minutes * 60 seconds = 86400 seconds), in a heavy traffic site, this can cause an Out Of Memory as everything will be held in memory until all of the data files have been loaded.

We have seen a few instances where the configured 5 seconds for Realtime has caused some problems due to SMDR events, the major symptom found was that it looks like SMDR based Statistics would stop updating, but the rest of the system was working, this has been seen sometimes up to 3 to 4 hours long.  We've found setting the value smaller has fixed the problems, just remember that the Realtime statistics can become less accurate.  Trigger a Manual Summary, or waiting for the Nightly Summary and running Reports will produce the correct Statistics.

There have been instances where the Realtime value was configured to 0 seconds.  This is a valid config, but it does and will effect the CallBack pegging in the Queue/Queue Group Now Monitors.  CallBacks require looking into the past to validate the peg, and if you set the SMDRReorderBufferReleaseIntervalInSeconds to 0 seconds, the Enterprise Server will not have anything in memory for the past to validate against so it'll never peg in Realtime.



CHANGING THE SETTING IN MiCC VERSION 6.X

NOTE:  Depending on whether you are changing this value for Realtime or Data Summarization you will need to update a different service.  See below for details.

1. Go to [InstallDir]\CCM\Services\DataProcessor\ for Data Summarization, or [InstallDir]\CCM\Services\EnterpriseServer\ for Realtime.
2. Make a copy of DataService.exe.config or prairieFyre.Services.EnterpriseServer.exe.config as a backup.
3. Edit DataService.exe.config or prairieFyre.Services.EnterpriseServer.exe.config in notepad.
4. Locate the line <add key="SMDRReorderBufferReleaseIntervalInSeconds" value="##" /> where ## is the current value.
5. Edit the number beside value= to the desired time.
6. Save the file.
7. Ensure that the Data Processor service is stopped, or .NET Enterprise Server service is restarted.
8. Re-summarize the data you want to apply the new SMDR Reorder Buffer value to (for Data Summarization.  All new data coming in will be affected for Realtime).

CHANGING THE SETTING IN MiCC VERSION 7.X OR NEWER

1. Go to [InstallDir]\Services\ConfigService\ .
2. Launch the GlobalApplicationSettingsEditor.exe .
3. Fill in the following details:

  • application: DataService.exe or prairieFyre.Services.EnterpriseServer.exe 
  • SectionGroup: appSettings
  • Name: SMDRReorderBufferReleaseIntervalInSeconds
  • Value: ### (where ### is the value in seconds that you want)
  • Description: Enter a quick description of who/why is making this change.

4. Click SaveNOTE: It can take up to 30 seconds for the save to take effect.  Wait for the confirmation prompt, and click OK.


APPLIES TO

6.0, and newer 

Keywords: SMDR reorder buffer SMDRReorderBufferReleaseIntervalInSeconds manual config configuration summarize summarization

License not converted when changing from 7.X (or older) to 8.1 (or newer) in AMC.

Next: HotFix KB388947 - After applying HotFix KB383468, MCC Chat account codes no longer being reported
Previous: HowTo - SMDR Reorder Buffer for Data Summarization
$
0
0
Article ID:  - Last Review: March 3, 2017

PROBLEM

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


 

WORKAROUND



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

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



RESOLUTION

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



APPLIES TO

AMC, MiCC 8.1 

Keywords: AMC conversion license update

HotFix KB388947 - After applying HotFix KB383468, MCC Chat account codes no longer being reported

Next: HotFix KB386779 - Data from 7.1 system will no longer summarize in 8.1.1.0
Previous: License not converted when changing from 7.X (or older) to 8.1 (or newer) in AMC.
$
0
0
Article ID: 52531 - Last Review: March 15, 2017

PROBLEM

After applying HotFix KB383468, MCC Chat account codes are no longer reporting. 



RESOLUTION

This HotFix is to be installed onto MiContact Center Business Version 8.1.0.0 with KB383468

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

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



APPLIES TO

MiCC 8.1.0.0 KB383468 

Keywords: hotfix kb388947 388947 chat mcc account code codes

HotFix KB386779 - Data from 7.1 system will no longer summarize in 8.1.1.0

Next: HotFix KB392367 - IVR Menu and Collect Digit activities' timeout value is not configurable when voice recognition is enabled
Previous: HotFix KB388947 - After applying HotFix KB383468, MCC Chat account codes no longer being reported
$
0
0
Article ID: 52532 - Last Review: March 15, 2017

PROBLEM

Some data from a MiContact Center 7.1 system would no longer summarize after it was upgraded to 8.1.1.0



RESOLUTION

This HotFix is to be installed onto MiContact Center Business Version 8.1.1.0

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

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



APPLIES TO

MiCC 8.1.1.0

Keywords: hotfix KB386779 386779 summarize

HotFix KB392367 - IVR Menu and Collect Digit activities' timeout value is not configurable when voice recognition is enabled

Next: DNIS information is showing the destination digits instead of the original 10 digits dialed after upgrading MiVoice Business to 8.0.
Previous: HotFix KB386779 - Data from 7.1 system will no longer summarize in 8.1.1.0
$
0
0
Article ID: 52533 - Last Review: March 20, 2017

PROBLEM

When voice recognition is enabled, users cannot configure the Timeout value in IVR Menu and Collected Digit activities. 



RESOLUTION

This HotFix is to be installed onto MiContact Center Business Version 8.1.1.0

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

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



APPLIES TO

MiCC 8.1.1.0 

Keywords: 392367 KB392367 voice recognition menu collected digits timeout

DNIS information is showing the destination digits instead of the original 10 digits dialed after upgrading MiVoice Business to 8.0.

Next: PBX programming-related error messages for CCC softphone
Previous: HotFix KB392367 - IVR Menu and Collect Digit activities' timeout value is not configurable when voice recognition is enabled
$
0
0
Article ID: 52534 - Last Review: March 23, 2017

PROBLEM

The DNIS information for a call is showing the destination digits instead of the original 10 digits dialed. 

The MiVoice Business was recently upgraded to version 8.0.



RESOLUTION

A software fix will be provided in MiVoice Business version 8.0 SP1. 



APPLIES TO

MiCC, 8.X and newer 

Keywords: DNIS MiVB mivoice business


PBX programming-related error messages for CCC softphone

Next: Detailed Release Notes for MiContact Center for MiVoice Business 8.1.2.0
Previous: DNIS information is showing the destination digits instead of the original 10 digits dialed after upgrading MiVoice Business to 8.0.
$
0
0

Common CCC softphone error codes related to PBX programming

 

Problem

When attempting to start the softphone, you get the following error:

Error type: eCommsError

Error code: -1

Operation:  RealtimeCallControlClient - WaitOnPendingWorkItem

Detailed message: System.TimeoutException: Softphone proxy server did not respond after 30 seconds

 

If you look at the Mitai proxy server logs on the server, you find the following error:

eError: …              MiTAIEngine - SetExtnMonCallback:       Failed to monitor device - DN:[xxxx] ReturnCode:[SXERR_PRIVILEGE_VIOLATION] Hmon:[…]

Cause

The Mitai proxy server fails to set the monitor on the requested extension because it is associated to a class of service on the PBX that has “HCI/CTI/TAPI call control allowed” and “HCI/CTI/TAPI monitor allowed” set to false.

Resolution

Either modify the class of service for the associated extension so that “HCI/CTI/TAPI call control allowed” and “HCI/CTI/TAPI monitor allowed” are set to true, or create a brand new class of service with the mentioned properties set to true.

--------------------

Problem

When attempting to start the softphone, you get the following error:

Error type: eMitaiError

Error code: 1245

Operation:  GetForwardFeatureInfo

 

If you look at the CCC log, you will find the following error:

eError: …              SoftphoneConfig::populateForwardingInfo:        Operation failed - MessageTag:[3] ReturnCode:[SXERR_FEATURE_NOT_ALLOWED]

Cause

The Mitai proxy server fails to set the monitor on the requested extension because the prime line for that extension is a member of a multicall group that is linked to another extension.  This causes the mitai monitor to be set on the group DN, instead of on the requested extension.  Then, when trying to get the forwarding info for that extension, Mitai fails because it tries to get forwarding information from the group, which is not possible.

Resolution

Change the prime line of that extension to be a single line.  If the multicall group has to remain, simply create it as a secondary line appearance on the extension.

--------------------

Problem

After the CCC softphone is started, when attempting to use the ACD actions menu to log in as an ACD agent, you get the following error:

Failed to login using the specified ACD agent, some of the possible reasons include are

                - The specified agent ID is used somewhere else

                - There is already an ACD agent logged in to this phone

                - This phone is not enabled for ACD login

 

If you look at the CCC logs, you will find the following error:

eError: …              MiniPhoneView::mnuSubACDLogin_Click:            Operation failed - MessageTag:[5] ReturnCode:[SXERR_PRIVILEGE_VIOLATION]

Cause

The mitai proxy server fails to login the extension with the specified agent because the extension itself is not enabled for ACD.

Resolution

Make sure the “ACD enabled” feature on the associated extension is turned on.


For tagging purposes:

sxerr privilege violation MiTAI softphone

Detailed Release Notes for MiContact Center for MiVoice Business 8.1.2.0

Next: Supported MiVoice Business (MCD) releases by MiCC Version
Previous: PBX programming-related error messages for CCC softphone
$
0
0
Article ID: 52535 - Last Review: March 27, 2017

INFORMATION

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


 

APPLIES TO

MiCC 8.1.2.0

Keywords: DRN 8.1.1.0 release notes

Supported MiVoice Business (MCD) releases by MiCC Version

Next: Pre-Requisite Software Compatibility by MiCC Version
Previous: Detailed Release Notes for MiContact Center for MiVoice Business 8.1.2.0
$
0
0
Article ID: 51183 - Last Review: March 25, 2017

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 only), 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 newer)**, MCD 7.0 through MCD 7.0 SP1, MCD 7.1*, MCD 7.2, MCD 7.2 SP1, and MCD 8.0
MiCC 8.1.0.0MCD 6.0 SP3 (12.0.3.24 or newer)**, MCD 7.0 through MCD 7.0 SP1, MCD 7.1*, MCD 7.2, MCD 7.2 SP1, and MCD 8.0
MiCC 8.1.1.0MCD 6.0 SP3 (12.0.3.24 or newer)**, MCD 7.0 through MCD 7.0 SP1, MCD 7.1*, MCD 7.2, MCD 7.2 SP1, and MCD 8.0
MiCC 8.1.2.0MCD 6.0 SP3 (12.0.3.24 or newer)**, MCD 7.0 through MCD 7.0 SP1, MCD 7.1*, MCD 7.2, MCD 7.2 SP1, and MCD 8.0

*MCD 7.1 PR1 is not compatible with MiCC CCM (see http://micc.mitel.com/kb/KnowledgebaseArticle52315.aspx).  We have corrected this in MCD 7.1 PR2 and newer.
** MCD 12.0.3.24 is a patch load.  In order to download this load you will need to contact MiVoice Business support.

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

Pre-Requisite Software Compatibility by MiCC Version

Next: Client and Server Port Requirements
Previous: Supported MiVoice Business (MCD) releases by MiCC Version
$
0
0
Article ID: 51491 - Last Review: , March 25, 2017

INFORMATION

The following tables show what versions of .NET, IE, SQL, Windows (Server), and Windows (Client) are supported by version of prairieFyre software.  Please note that a * indicates that it is only partially supported and you should check the System Engineering Guide for more details.  In cases where the table shows Yes SP# this means that it is supported, and has been tested additionally up to the SP# as well.  When in doubt, always check your System Engineering Guide for more detail.

.NET Framework

 5.7 GA 5.7 SP1 5.8.0.X 6.0.X.X 7.0.X.X7.1.X.X8.0.0.08.1.0.08.1.2.0
3.5 SP1  Yes Yes Yes Yes Yes Yes Yes Yes Yes
4.0  No No No Yes Yes Yes Yes Yes Yes
4.5 No No No Yes* Yes Yes Yes Yes Yes
4.6 No No No No No No No Yes Yes

Internet Explorer
 5.7 GA 5.7 SP1 5.8.0.X 6.0.X.X 7.0.X.X7.1.X.X8.0.0.08.1.0.08.1.2.0
IE 6  Yes Yes Yes Yes No No No No No
IE 7  Yes Yes Yes Yes No No No No No
IE 8  Yes Yes Yes Yes Yes Yes (up to 7.1.0.1 only) No No No
IE 9  No No No Yes Yes Yes No No No
IE 10 No No No Yes* Yes Yes Yes Yes Yes
IE 11 No No No No Yes Yes Yes Yes Yes
Edge No No No No No No No Yes Yes

NOTE: With MiCC Version 7.1 and newer we recommend using IE10 or newer.  Older versions will work for the most part, but some controls are affected.  An example of this is the manual EMail Address field under report distribution being a non-editable field.  For sites using Multimedia or the Ignite client we recommend IE11 for best performance and compatibility.

SQL Server

5.7 GA 5.7 SP1 5.8.0.X 6.0.0.X 6.0.1.X7.0.X.X7.1.X.X8.0.0.08.1.0.08.1.2.0
2005 Express  Yes Yes Yes Yes Yes No No No No No
2008 Express  Yes Yes Yes Yes Yes Yes No No No No
2008 Express R2  Yes Yes Yes Yes Yes Yes No No No No
2005 SP3 Yes Yes Yes Yes SP4 Yes No No No No No
2008 SP1 Yes Yes Yes Yes Yes Yes Yes No No No
2008 R2  Yes Yes Yes Yes SP1 Yes Yes Yes No No No
2012 Express No No No No Yes Yes Yes Yes Yes Yes
2012 No No No No Yes Yes Yes Yes Yes Yes
2014 Express No No No No No No Yes Yes Yes Yes
2014 No No No No No No Yes Yes Yes Yes
2016 No No No No No No No No No Yes
2016 Express No No No No No No No No No Yes

Excel
5.7 GA 5.7 SP1 5.8.0.X 6.0.X.X 7.0.X.X7.1.X.X8.0.0.08.1.0.08.1.2.0
2003 SP2 Yes Yes  Yes Yes No No No No No
2007 SP2 Yes Yes Yes Yes Yes Yes No No No
2010  No No No Yes Yes Yes YesYesYes
2013 No No No No Yes Yes YesYesYes
2016 No No No No No No NoYesYes

Windows on the Server
5.7 GA 5.7 SP1 5.8.0.X 6.0.0.X 6.0.2.X7.0.X.X7.1.X.X8.0.0.08.1.0.08.1.2.0
XP Pro SP3  Yes* Yes* Yes* No No No No No No No
2003 R2 (32-bit) Yes SP1 Yes SP1 Yes Sp2 Yes Sp2 Yes Sp2 No No No No No
2008 SP2 (32-bit) Yes Yes Yes Yes Yes No No No No No
2008 R2 (64-bit) No No No Yes Yes Yes Yes Yes Yes* Yes*
Windows 7 32-bit Yes* Yes* Yes* Yes* Yes* No No No No No
Windows 7 64-bit No No No Yes* Yes* Yes* Yes* No No No
Small Business 2011  No No No Yes Yes* No No No No No
Windows 2012 No No No No Yes Yes Yes Yes Yes Yes
Windows 2012 R2 No No No No Yes Yes Yes Yes Yes Yes
Windows 8 32-bit No No No No Yes* No No No No No
Windows 8 64-bit No No No No Yes* Yes* Yes* No No No
Windows 8.1 64-bit No No No No No Yes* Yes* No No No
Windows 8.1 32-bit No No No No No No No No No No
Server 2016 No No No No No No No No No Yes

Windows on the Client

5.7 GA 5.7 SP1 5.8.0.X 6.0.0.X 6.0.2.X7.0.X.X7.1.X.X7.1.3.38.0.0.08.1.0.08.1.2.0
XP Pro  Yes Yes Yes Yes Yes No No No No No No
Vista 32-bit  Yes Yes Yes Yes Yes Yes Yes Yes No No No
Vista 64-bit  No Yes Yes Yes Yes Yes Yes Yes No No No
Windows 7 32-bit  Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes* Yes*
Windows 7 64-bit  No Yes Yes Yes Yes Yes Yes Yes Yes Yes Yes
Windows 8 32-bit No No No No Yes Yes Yes Yes Yes Yes* Yes*
Windows 8 64-bit No No No No Yes Yes Yes Yes Yes Yes Yes
Windows 8.1 32-bit No No No No No Yes Yes Yes Yes Yes* Yes*
Windows 8.1 64-bit No No No No No Yes Yes Yes Yes Yes Yes
Windows 10 No No No No No No No Yes Yes Yes Yes

PBX Compatibility
 5.7 GA 5.7 SP1 5.8.0.X 6.0.X.X 7.0.X.X7.1.X.X8.0.0.08.1.0.08.1.2.0
3300 ICP  Yes Yes Yes Yes Yes Yes Yes Yes Yes
SX-200  Yes Yes Yes Yes* No No No No No
SX-2000  Yes* Yes* Yes* No No No No No No
5000/Axxess Yes* Yes* Yes Yes No No No No No


For Mitel 3300 ICP software compatibility by version, please refer to Knowledgebase Article 51183.

APPLIES TO

CCM 5.7 GA, 5.7 SP1, 5.8, 6.0, 7.0, 7.1, 8.0, 8.1

Keywords: compatibility .NET Windows SQL IE internet explorer excel

Client and Server Port Requirements

Next: HotFix KB389019 - Multiple Multimedia fixes for MiContact Center Version 8.0.1.0
Previous: Pre-Requisite Software Compatibility by MiCC Version
$
0
0
Article ID: 51887 - Last Review: April 3, 2017

 

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

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

Table 1 - Unique Port List


Port

Protocol

Description

21

TCP

FTP connectivity for third party Workforce Management services

25

TCP

SMTP connection for alarms and report distribution

80

TCP

HTTP traffic for CCMWeb

389

TCP

LDAP

587

TCP

Used to send automatic e-mail alarms (When using SSL)

1433

TCP

SQL Traffic

1443

TCP

SQL Traffic

1719-1720

TCP

Freeswitch (MiCC 8.1 and up)

1752

TCP

SMDR data collection from PBX

1754

TCP

Traffic data collection from PBX

3478-3479

TCP

Freeswitch (MiCC 8.1 and up)

5000-5010

TCP

Contact Center Client

5022

TCP

Web Chat requests

5024

TCP

Real time data stream

5025

TCP

Auditor data stream

5026

TCP

Call control

5030

TCP

Call recording control

5050

TCP

Multimedia Contact Center communication

5060

TCP

Freeswitch (MiCC 8.1 and up)

5066

TCP

Freeswitch (MiCC 8.1 and up)

5070

TCP

Freeswitch (MiCC 8.1 and up)

5080

TCP

Freeswitch (MiCC 8.1 and up)

5152

TCP

Multimedia Contact Center communication

5320

TCP

MiTAI communications (MiCC 8.0 and newer)

5400

TCP

Data stream from remote collector services

6999

TCP

Used to stream real time data to third party Workforce Management applications

7000

TCP

Configuration service and authentication

7001

TCP

Configuration service and authentication

7002

TCP

Configuration service and authentication

7003

TCP

Configuration service and authentication

7004

TCP

IVR Updater service

7011

TCP

Data syncronization with PBX

7443

TCP

Freeswitch (MiCC 8.1 and up)

8000-8001

TCP

MiTAI connection to PBX (MiCC 7.1 and older)

8002

TCP

Server Monitoring Agent

8021

TCP

Freeswitch (MiCC 8.1 and up)

8080

TCP

Freeswitch (MiCC 8.1 and up)

8083

TCP

Callback management and messaging

8084-8085

TCP

Callback management and messaging

8188

TCP

Professional Services dialer port

10001

TCP

Connecting to Wallboard

10118

TCP

Client communication to Exchange for MCC ACD

15373

TCP

ACD data collection from PBX

16384-32768

TCP

Freeswitch (MiCC 8.1 and up)

35001

TCP

External connections to the Mitel Border Gateway on this port translate to port 5030 to the CCM Server inside the corporate network

35002

TCP

External connections to the Mitel Border Gateway on this port translate to port 7001 to the CCM Server inside the corporate network

35003

TCP

External connections to the Mitel Border Gateway on this port translate to port 7003 to the CCM Server inside the corporate network

35004

TCP

External connections to the Mitel Border Gateway on this port translate to port 8083 to the CCM Server inside the corporate network

35005

TCP

External connections to the Mitel Border Gateway on this port translate to port 8084 to the CCM Server inside the corporate network

35006

TCP

External connections to the Mitel Border Gateway on this port translate to port 42440 to the CCM Server inside the corporate network

35008

TCP

External connections to the Mitel Border Gateway on this port translate to port 8188 to the CCM Server inside the corporate network

36000

TCP

External connections to the Mitel Border Gateway on this port translate to port 80 to the CCM Server inside the corporate network

36001

TCP

External connections to the Mitel Border Gateway on this port translate to port 443 to the CCM Server inside the corporate network

36002

TCP

External connections to the Mitel Border Gateway on this port translate to port 5024 to the CCM Server inside the corporate network

36003

TCP

External connections to the Mitel Border Gateway on this port translate to port 5025 to the CCM Server inside the corporate network

36004

TCP

External connections to the Mitel Border Gateway on this port translate to port 5026 to the CCM Server inside the corporate network

42440

TCP

WFS Client connectivity

50122

TCP

WFS Client connectivity

1433-1434

UDP

SQL Server Traffic

3268-3269

TCP

LDAP Connection

50000-50511

UDP

Console Voice Channel for voice communication to PBX

6800-6803

TCP

MiNET connection to Mitel PBX

9000-9001

UDP

Phone media RTP for voice communication to PBX

9200

TCP

Elasticsearch (MiCC 8.X and up)

9300

TCP

Elasticsearch (MiCC 8.X and up)

Table 2 - Deployment Scenarios

CCM Enterprise Server

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

 

CCM Enterprise Serverwith IVR

  

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

 

 

CCM Enterprise withIVR & MCC

 

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

 

 

Remote ServerSoftware

 

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

 

 

Client Installations

 

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


 

Revision Notes:

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

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

Viewing all 453 articles
Browse latest View live