Mitel Unified Communicator


To automatically call out from PowerForce into the Mitel Softphone.

Getting There:

[ SC ] –> Modules / Module Options


For those customers that have a Mitel Communicator Advanced switch, PowerForce has the ability to auto-dial the client or employee through the Scheduling Workbench.

The solution is quite simple, with each user having to run a Mitel application on their desktop to access the phones, we add a simple .dll registration at the workstation, and that provides a means for PowerForce to be able to interface into the Mitel call / dial a number function.


Top of Page

Scheduling Workbench

On the scheduling workbench, you have two icons which represent phones, one below the client / site and the other below the employee details.

swb Pressing on the phone icon, will bring up either the client or employee details.

swbFor those instances where the client / employee has more than one contact number, select the number that you wish to call out to, and then press the "Dial" button. This will then pass the phone number from PowerForce across into the Mitel Communicator to dial out (below).

The Mitel applicaiton then shows you the number about to be dialed, press OK to proceed.


Client Workstation Requirements

The interface from PowerForce to the switch works via the Unified Communicator application running on the users desktop, and requires one of the Mitel .dll files to be registered for the user at the workstation.


The requirements are as follows:

  • The MITEL software will install the following .dll somewhere into "<system drive>\Program Files\Mitel\*", "TelephonyProxy.dll". Where <system drive> is usually "C:", and the "*" means wildcard.
  • You need to execute the following command to register this .dll into the users "hive"

    regasm TelephonyProxy.dll /codebase .

  • You will find regasm.exe in "<system drive>\Microsoft.Net\Framework\*", where * represents the latest version number. If you have more than one sub-directory to the Frameworks, select the highest version number, though we've comfortably registered using the v2.0 of .Net, when the workstation itself was on v4.0 of the .Net Framework.

Top of Page

See Also