Issues encountered while configuring CLICK2CALL in UCM and how to resolve them

While I was configuring CLICK2CALLwith UCM6302 in my environment, I encountered several issues, and I managed to fix them along the way. I hope this guide will be helpful for those who are facing the same issues as me.

1. Call icon Stuck in ‘calling’

Issue –

The webserver used here is IIS. Configuration was double verified with my previous how-to guide, and there was no mistake on the configuration side.

However, when I clicked on the call icon, it was stuck in ‘calling’. No calls were coming into the UCM, as shown under Active calls.

Upon inspecting the console on the webpage, I found out that I am hitting a RunTimeError –

Reason –

It was stuck in calling is because by default IIS does not have a content type for WASM extension.

Resolution –

Adding "application/wasm" for the WASM extension fixes the issue. (I note that IIS Express uses "application/octet-stream" as the mime type, but it doesn't look like there is a standard yet.)

It should look like this after adding “application/wasm" for the WASM extension file.

<mimeMap fileExtension=".wasm" mimeType="application/wasm" />

2. Clicking on the Call button does not prompt anything

Issue –

Click on the call button does not do anything/ respond. It does not prompts the microphone and speaker check test and does not proceed to call as well. Tested with Mozilla Firefox and Google Chrome, and the issue was happening to both bowsers.

I found out that I was hitting an Uncaught TypeError from the browsers –

Reason –

There are two resolutions for this:

1. Access the webpage using HTTPS instead of HTTP

You will need to make some configurations on your IIS side to ensure that the webpage can be accessed with HTTPS

2. Modifying the browser security configuration (Direct and Simple way)

i. Input in the browser address bar:

chrome://flags/#unsafely-treat-insecure-origin-as-secure

ii. Turn on Insecure origins treated as secure

iii: Relaunch the browser