Mitel MiCC-B Integration Guide

1. Ensure MiCC is on version 9 or higher

Version 9.0 (or higher) of MiCC is required for access to the Open Media API. Web Ignite is also required. Multimedia licences are required for agents.

2. Apply TLS certificate to MiCC server

You must provide a TLS CA certificate and provide an FQDN for the server.

3. Talkative connection to MiCC

Talkative needs to send HTTPS requests through to MiCC. To do this, Talkative recommends port forwarding. Only port 443 will be required by Talkative. The traffic will be REST HTTPS requests to the "MiCC SDK" API interface. An out-of-range port can be used, and one locked down to the Talkative IP (in AWS). No sensitive data will be sent via this route. Talkative operates multiple instances, please use the correct IP addresses from the list below for your region.

Europe: Requests will originate from 3.8.11.116 AND 3.8.226.26 - please add both IP addresses.

USA: Requests will originate from 3.20.102.7 AND 3.20.102.37 - please add both IP addresses.

Australia: Requests will originate from 13.55.255.55 AND 13.55.255.70 - please add both IP addresses.

More regions are being added soon, please contact Talkative for more details.

4. MiCC Open Media Config

1. Create an OpenMedia media server. 
2. Create OpenMedia agents. 
3. Create OpenMedia queues and assign groups. 
4. Create OpenMedia workloads for agents.
5. Adjust Inbound and in-queue workflows to client needs. 
6. Authorisation of the Talkative client within MiCC. 

NB: When creating Queues, please make sure you select the “Validate Workflow” option from the Properties Tab. If this is not selected, the changes you make will not be published and the Queue will be unable to receive interactions from Talkative. This option must be selected for “Inqueue Workflow” and “Agent Workflow”.

To set up an OpenMedia queue:

1. Inside YourSiteExplorer open the "Queues" menu (which can be located under the Multimedia tab on the left).
2. Click "Add" and then select "Open Media Queue”.
3. Fill in the "Name" and "Reporting Number”.
4. Under "Inqueue Workflow" right click "Offer To Primary Agent Group" then select "Agent Group" and then select the OM agent group you created earlier.
5. Still under "Inqueue Workflow", in the properties tab of the right must then tick "Validate Workflow”.
6. Lastly, save the new queue (rest of the settings can be left default or customised however you like).

Once the OpenMedia queue is set up make sure that it is also attached as the last resort queue on the OM Media Server. This is done by navigating to the "Media Servers" page. Select the Open Media server, then right click on the "Routing Failure Destination Transfer" tool in the inbound workflow and then set the newly created queue as the destination.

To authorise the client:

Find C:\Program Files (x86)\Mitel\MiContact Center\WebSites\AuthorizationServer\Configuration\Clients.config

Add a value for Talkative. Example:

{

    "Id": "Talkative",

    "Secret": "********-****-****-****-********"

 }

After this value has been added, you should restart the IIS server and recycle the app pool for authorisation service.

The Secret key is in Version 4 UUID format and is unique to each organisation. Talkative will provide you with a Secret key via email (support@talkative.uk ) or you can create your own UUID here: https://www.uuidgenerator.net/version4  

Within Talkative, visit https://eu.engage.app/company/distributor-configs/create (accessed via Company Manager -> Distributor Config -> Mitel) or the same link within other regions, i.e. North America: https://us.engage.app/mitel-company-distributor-configs/create or ANZ: https://au.engage.app/company/distributor-configs/create 

• Enter in your MiCC URL
• Enter Talkative as the Client ID
• Enter Secret Key
• Enter a Queue Cap (any positive integer will suffice e.g. 10)
• Press submit and this will complete the authorisation process. 

Once the connection is set up, if you edit the integration, a link will now show up called "Manage all user settings to Mitel", which, when clicked, will let you correlate Talkative accounts with MiCC accounts: 

You will also need to correlate Talkative queues with MiCC OM queues in the Queues section of Talkative under the "Router Queue" dropdown:

You will now be able to proceed with the rest of the Talkative set up within the application, such as creating chat widgets, setting business hours etc.

Troubleshooting

Issue: When creating an interaction, a successful response is received from MiCC but the interaction does not get assigned to an agent and is not visible in any queues.

Solution:  Revisit step 4 of the Open Media queue set up process. This problem usually occurs when the “Validate Workflow” checkbox has not been ticked when creating a new OpenMedia queue. Ensure this checkbox is ticked and resolve any validation errors that appear.

Be sure to navigate to Multimedia > Media servers

Issue: Queue does not appear online in Talkative Engage

Solution: Check that the Queue has been assigned to the relevant Agent Groups within MiCC. The assigned groups will appear as Members under the General tab on the relevant queue.