SUMMARY

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 web applications such as CCMWeb or Web-Ignite
389	TCP	LDAP
443	TCP	HTTPS traffic for web applications such as CCMWeb or Web-Ignite
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)
4000-4999	TCP	Nuance (MiCC 9.0 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)
5090	TCP	Nuance (MiCC 9.0 and up)
5091	TCP	Nuance (MiCC 9.0 and up)
5092	TCP	Nuance (MiCC 9.0 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
9200	TCP	Elasticsearch (MiCC 8.X and up)
9300	TCP	Elasticsearch (MiCC 8.X and up)
10001	TCP	Connecting to Wallboard
10118	TCP	Client communication to Exchange for MCC ACD
15373	TCP	ACD data collection from PBX
18000	TCP	MiXML service for Telephone System Settings Sycnhronization
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
46600-49500	TCP	MiTAI communications with the MiVoice Business (MiCC 8.X and newer)
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
• 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
May 22, 2018 - Added SSL for web applications, MiXML for sync, minor formatting cleanup.
 

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

PROBLEM

This HotFix addresses an issue where users were unable to access the Security Role configuration screens in YourSite Explorer when SSL was enabled, as well as security roles blocking access to Web-Ignite in error.  

RESOLUTION

This HotFix is to be installed onto MiContact Center Business version 8.1.4.0.

1. Ensure that KB441591 is installed.
2. Go to https://www.mitel.com/
3. Click the Log in button.
4. Click the Sign in button under Connect.
5. On the left, select the Software Download Center.
6. Expand the tree to MiContact Center Business and then down to MiContact Center Business 8.1.4.0 and HotFixes.
7. Download the MiCC HotFix KB442126.exe HotFix to the MiContact Center server.
8. Double-click the MiCC HotFix KB442126.exe and follow the on-screen prompts.
9. Wait for the repackager and auto-updates to complete. 

APPLIES TO

MiCC 8.1.4.0 

PROBLEM

The Agent Performance by Make Busy/DND report was sometimes failing to peg Make Busy counts, but still pegging duration. 

CAUSE

A race condition resulted in an ACD Ringing event arriving out of order conflicting with the Make Busy punch. 

RESOLUTION

This HotFix is to be applied onto MiContact Center Business version 8.1.4.0.

1. Ensure that KB428628 is installed.
2. Ensure that KB427310 is installed.
3. Ensure that KB435696 is installed.
4. Ensure that KB427400 is installed.
5. Go to https://www.mitel.com/
6. Click the Log in button.
7. Click the Sign in button under Connect.
8. On the left, select the Software Download Center.
9. Expand the tree to MiContact Center Business and then down to MiContact Center Business 8.1.4.0 and HotFixes.
10. Download the MiCC HotFix KB443688.exe HotFix to the MiContact Center server.
11. Double-click the MiCC HotFix KB443688.exe and follow the on-screen prompts.
12. Wait for the repackager and auto-updates to complete.

APPLIES TO

8.1.4.0 

DESCRIPTION

Report Meter Pulses is set to "Yes" on the PBX .

Select "Yes" if meter pulses are to be included in SMDR reports. The number of reversals (meter pulses) received from an outgoing trunk can be recorded when this option is selected. The range is 0 to 64000. Leading zeros are output. The maximum number of digits recorded reduces from 26 to 20. The trunk group must be programmed for “Answer Supervision”. This field is not used for internal SMDR. 

SEVERITY

Minor 

IMPACT

This option must be set to "No" for accurate reporting. If set incorrectly, five zeros will append to the digits dialed column of SMDR records.

TROUBLESHOOTING STEPS

1. Open the 3300 ESM.
2. On the left, click on System Properties =>System Feature Settings =>SMDR Options.
3. Click Change.
4. Set Report Meter Pulses to No.
5. Click Save.

APPLIES TO

6.0 SP1 

PROBLEM

This HotFix addresses two issues:

• A security list with Employee Groups assigned does not reflect changes in YourSite Explorer after leaving the security list page and coming back.
• Can not run Queue or Queue Group Lifecycle reports at all if a security list limiting Queue Groups is implemented.

RESOLUTION

This HotFix is to be installed onto MiContact Center Business version 8.1.4.0.

1. Ensure that KB426218 is installed
2. Go to https://www.mitel.com/
3. Click the Log in button.
4. Click the Sign in button under Connect.
5. On the left, select the Software Download Center.
6. Expand the tree to MiContact Center Business and then down to MiContact Center Business 8.1.4.0 and HotFixes.
7. Download the MiCC HotFix KB445970.exe HotFix to the MiContact Center server.
8. Double-click the MiCC HotFix KB445970.exe and follow the on-screen prompts.
9. Wait for the repackager and auto-updates to complete.

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

APPLIES TO

PROBLEM

Lifecycle and Trace data tables did not include the first digit of the ANI if that digit was a 1. 

RESOLUTION

This HotFix is to be installed onto MiContact Center Business version 8.1.4.0.

Ensure that KB428628 is installed.
Ensure that KB427310 is installed.
Ensure that KB435696 is installed.
Ensure that KB427400 is installed.
Go to https://www.mitel.com/
Click the Log in button.
Click the Sign in button under MiAccess.
On the left, select the Software Download Center.
Expand the tree to MiContact Center Business and then down to MiContact Center Business 8.1.4.0 and HotFixes.
Download the MiCC HotFix KB446964.exe HotFix to the MiContact Center server.
Double-click the MiCC HotFix KB446964.exe and follow the on-screen prompts.
Wait for the repackager and auto-updates to complete.

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

APPLIES TO

MiCC 8.1.4.0 

PROBLEM

You are looking to set the default Font and Font Size for all your Ignite clients. 

RESOLUTION 7.X

You can set a global default for these values via the GlobalAppSettingsEditor.  You can modify one or both of these values.

NOTE: The font type must be entered exactly as shown in the font drop down menu in ignite.

NOTE: Font sizes are a scale from 1 to 8.  The standard 'point' values for each number are as follows:
1 is 6pt
2 is 8pt
3 is 10pt
4 is 12pt
5 is 14pt
6 is 18pt
7 is 24pt
8 is 36pt

To add the values to your configuration, please do the following (note that if only adding one value, you skip the step for entering the other):

1. Go to [InstallDir]\CCM\Services\ConfigService\ and open the GlobalAppSettingsEditor.
2. Fill in the following settings on a new line if you wish to specify the default Font Size:

• Application: (Leave this box empty)
• SectionGroup: appSettings
• Name: FontSize
• Value: A number from 1 to 8 or default
• Description: An explanation of why the change is being implemented. Note that you must enter a value here to save.

NOTE: Deleting this line in the Global Application Settings Editor will not set the system back to default.  To do that, use default as the value.

3. Fill in the following settings on a new line if you wish to specify the default Font Type:

• Application: (Leave this box empty)
• SectionGroup: appSettings
• Name: FontType
• Value:(Enter the font name, as it appears in the drop-down menu in Ignite)
• Description:An explanation of why the change is being implemented. Note that you must enter a value here to save.

NOTE: Deleting this line in the Global Application Settings Editor will not set the system back to default.  To do that, use default as the value.

4. Click Save.  It will take 30 to 60 seconds to save.  Please wait for the confirmation box before closing the Editor.

RESOLUTION 7.1.3.X and 8.X

NOTE: In Version 8.0.0.0 the Value format has changed.  You are now specifying the "point" size of the font formatted like this:  12pt .

To add the values to your configuration, please do the following (note that if only adding one value, you skip the step for entering the other):

1. Go to [InstallDir]\CCM\Services\ConfigService\ and open the GlobalAppSettingsEditor.
2. Fill in the following settings on a new line if you wish to specify the default Font Size:

• Application: (Leave this box empty)
• SectionGroup: appSettings
• Name: FontSize
• Value: The point value for the font size desired (eg: 12pt).  Or set it to default to restore the default value.
• Description: An explanation of why the change is being implemented. Note that you must enter a value here to save.

NOTE: Deleting this line in the Global Application Settings Editor will not set the system back to default.  To do that, use default as the value.

3. Fill in the following settings on a new line if you wish to specify the default Font Type:

• Application: (Leave this box empty)
• SectionGroup: appSettings
• Name: FontType
• Value:(Enter the font name, as it appears in the drop-down menu in Ignite)
• Description:An explanation of why the change is being implemented. Note that you must enter a value here to save.

NOTE: Deleting this line in the Global Application Settings Editor will not set the system back to default.  To do that, use default as the value.

4. Click Save.  It will take 30 to 60 seconds to save.  Please wait for the confirmation box before closing the Editor.

RESOLUTION 9.X

NOTE: In Version 9.0.0.0 the Value format is teh same as 8.X.  You specify the "point" size of the font formatted like this:  12pt .

To add the values to your configuration, please do the following (note that if only adding one value, you skip the step for entering the other):

1. Go to [InstallDir]\CCM\Services\ConfigService\ and open the GlobalAppSettingsEditor.
2. Fill in the following settings on a new line if you wish to specify the default Font Size:

• Application: (Leave this box empty)
• SectionGroup: Mitel.MiccSdk.Properties.Settings
• Name: EmailClientFontSize
• Value: The point value for the font size desired (eg: 12pt).  Or set it to default to restore the default value.
• Description: An explanation of why the change is being implemented. Note that you must enter a value here to save.

NOTE: Deleting this line in the Global Application Settings Editor will not set the system back to default.  To do that, use default as the value.

3. Fill in the following settings on a new line if you wish to specify the default Font Type:

• Application: (Leave this box empty)
• SectionGroup: Mitel.MiccSdk.Properties.Settings
• Name: EmailClientFontType
• Value:(Enter the font name, as it appears in the drop-down menu in Ignite)
• Description:An explanation of why the change is being implemented. Note that you must enter a value here to save.

NOTE: Deleting this line in the Global Application Settings Editor will not set the system back to default.  To do that, use default as the value.

4. Click Save.  It will take 30 to 60 seconds to save.  Please wait for the confirmation box before closing the Editor.

APPLIES TO

7.0 and newer

PROBLEM

When comparing the QueueNow monitor with an Agent State by Time, supervisors noticed in some cases a discrepancy with the number of Idle agents reported. 

RESOLUTION

This HotFix is to be applied onto MiContact Center Business version 9.0.1.0. 

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

APPLIES TO

MiCC 9.0.1.0 

PROBLEM

If an agent is in Work-Timer for a queue with forced classification codes and makes an outbound call an extra Non-Compliant classification code peg will be added to reports. 

RESOLUTION

This HotFix is to be installed onto MiContact Center Business version 8.1.4.0.

1. Ensure that KB428628 is installed.
2. Ensure that KB427310 is installed.
3. Ensure that KB435696 is installed.
4. Ensure that KB427400 is installed.
5. Go to https://www.mitel.com/
6. Click the Login button.
7. Click the Sign in button under MiAccess.
8. On the left, select the Software Download Center.
9. Expand the tree to MiContact Center Business and then down to MiContact Center Business 8.1.3.0 and HotFixes.
10. Download the MiCC HotFix KB445449.exe HotFix to the MiContact Center server.
11. Double-click the MiCC HotFix KB445449.exe and follow the on-screen prompts.
12. Wait for the repackager and auto-updates to complete.

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

APPLIES TO

MiContact Center Business 8.1.4.0 

PROBLEM

Intermittently a workflow was repeating each step for a single call.

RESOLUTION

This HotFix is to be applied onto MiContact Center Business version 8.1.4.0.

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

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

APPLIES TO

MiCC 8.1.4.0 

PROBLEM

MKB/DND Pegs and Durations not adding up when comparing Agent Group by Agent by MakeBusyDnDCode (or Agent MakeBusyDND Trace) with Agent (or Agent Group) Event by Period report.

RESOLUTION

NOTE:  This issue is already resolved in MiContact Center Business version 9.0.0.0 and later.  You only need this HotFix if you cannot upgrade to 9.0.

This HotFix is to be installed onto MiContact Center Business version 8.1.4.0. 

1. Ensure that KB428628 is installed.
2. Ensure that KB427310 is installed.
3. Ensure that KB435696 is installed.
4. Ensure that KB427400 is installed.
5. Go to https://www.mitel.com/
6. Click the Login button.
7. Click the Sign in button under MiAccess.
8. On the left, select the Software Download Center.
9. Expand the tree to MiContact Center Business and then down to MiContact Center Business 8.1.4.0 and HotFixes.
10. Download the MiCC HotFix KB455553.exe HotFix to the MiContact Center server.
11. Double-click the MiCC HotFix KB455553.exe and follow the on-screen prompts.
12. Wait for the repackager and auto-updates to complete.

APPLIES TO

MiCC 8.1.4.0 

Article ID: 52451 - Last Review: August 13, 2018

INFORMATION

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

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

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

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

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

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

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

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

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

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

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

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

APPLIES TO

MiCC Webchat Version 8.0 and newer 

PROBLEM

Multiple reports show zero when applying any call type filtering.

RESOLUTION

This HotFix is to be installed onto MiContact Center Business version 8.1.4.0.

1. Ensure that KB441591 is installed.
2. Ensure that KB442126 is installed.
3. Ensure that KB445970 is installed.
4. Go to https://www.mitel.com/
5. Click the Login button.
6. Click the Sign in button under MiAccess.
7. On the left, select the Software Download Center.
8. Expand the tree to MiContact Center Business and then down to MiContact Center Business 8.1.4.0 and HotFixes.
9. Download the MiCC HotFix KB455533.exe HotFix to the MiContact Center server.
10. Double-click the MiCC HotFix KB455533.exe and follow the on-screen prompts.
11. Wait for the repackager and auto-updates to complete. 

APPLIES TO

MiCC 8.1.4.0 

PROBLEM

In some cases multiple RoutingOutbound ports would pick up the same callback and attempt to process it at the same time. 

RESOLUTION

This HotFix is to be installed onto MiContact Center Business version 9.0.1.0. 

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

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

APPLIES TO

MiCC 9.0.1.0 

INFORMATION

The attached document contains the detailed release notes for MiContact Center Business version 9.0.0.0 

• MiVoice Office 400
• MiVoice Office 5000
• MiCloud

APPLIES TO

MiCC 9.0.0.0 

INFORMATION

The attached document contains the detailed release notes for MiContact Center Business version 8.1.4.1.

NOTE: This release is a rollup of a number of hotfixes from 8.1.4.0, and as such only has one DRN document.  If you require specific compatibility or install instructions for MiVB or SIP, please consult the 8.1.4.0 DRN.

APPLIES TO

 MiCC 8.1.4.1

PROBLEM

When a user on an Android phone reached the landing page for a Chat, the ghost text would not clear down, resulting in the chatter's information being appended to the end. 

RESOLUTION

WORKAROUND:  If the chatter moves their cursor to the very beginning of the field, they can then clear it. 

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

APPLIES TO

MiCC 8.1.4.1 

INFORMATION

Please see the attached DRN document for details on the MiContact Center Business version 9.0.2.0 release,. 

APPLIES TO

MiCC 9.0.2.0 

DESCRIPTION

This alarm indicates that the certificate for the Lync router server is going to expire.
 
NOTE: This alarm is not in use.

SEVERITY

Minor/Major/Critical can be configured in YourSite Explorer.

IMPACT

If the certificate is allowed to expire the Lync router might lose the connection with the domain and stop routing calls.

TROUBLESHOOTING STEPS

The router server needs to renew its certificate with the Domain. 

APPLIES TO

CCM 6.1 (Never released)

INFORMATION

If your Enterprise Server and Remote servers reside in a FIPS environment, Contact Center Solutions and Business Reporter requires a configuration change be made in your Window .NET Framework files to enable Contact Center Solutions and Business Reporter servers to communicate with each other and with client computers within the FIPS environment. Contact Center Solutions and Business Reporter are not FIPS-compliant; this configuration enables Contact Center Solutions and Business Reporter servers to function within a FIPS environment. This configuring only needs to be made once for an installation or upgrade as future upgrades will keep this setting.

NOTE:  If you update your version of .NET Framework, you make the configuration change again.

To enable Contact Center Solutions or Business Reporter in a FIPS environment

1. On your Enterprise Server or Remote Server, navigate to Windows\Microsoft.NET\Framework\2.0<version>\CONFIG.
    NOTE: The 2.0 folder’s name varies depending upon your .NET Framework version.
2. Open machine.config in an editor.
3. Add the following xml:
    <runtime>
        <enforceFIPSPolicy enabled="false"/>
    </runtime>
4. Save and close the editor.
5. Navigate to Windows\Microsoft.NET\Framework\4.0<version>\CONFIG.
    NOTE: The 4.0 folder’s name varies depending up your .NET Framework version.
6. Open machine.config in an editor.
7. Add the following xml:
    <runtime>
        <enforceFIPSPolicy enabled="false"/>
    </runtime>
8. Save and close the editor.
9. Repeat steps 5 through 8 for the file found in Windows\Microsoft.NET\Framework64\4.0<version>\CONFIG
10. Reboot your server.

APPLIES TO

7.1